Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

SOLVED Debugger does not pauses/stops the target (via GDB)

<< < (2/2)

MasterAlexei:

--- Quote from: oBFusCATed on February 01, 2014, 06:05:44 pm ---Have you put the commands in the initial commands field?
If you have then, C::B doesn't know you're in remote debugging mode and does the wrong thing when trying to break the inferior.

Go to Project -> Properties -> Debugger -> Remote debugging and set the connection from there.

--- End quote ---
That is the way i do almost 3 years already. As I already said, with the yagarto 4.7.2 gdb it works fine, with the newest gcc gdb 4.8 it does not. What I remembered yet is that for two years I did some changes in the debuggergdb plugin of C::B which does not hide the console window of the gdb. And this did work at that time, but since some revisions it was not necessary anymore. It seems that it will be necessary now.

oBFusCATed:
But if you've setup the remote debugging then m_State.GetDriver()->UseDebugBreakProcess() should return false and then you won't hit line 1631, but line 1646.
Is this the case?

As far as I remember, I was able to hide the console window, back in then when I've implemented this feature.
Also I don't think there are any changes to the handling of remote debugging lately (last 6 months).

Lastly: If you have any patches, it might be good idea to show them, so we can try to integrate them in the official release.

MasterAlexei:

--- Quote from: oBFusCATed on February 01, 2014, 06:25:47 pm ---But if you've setup the remote debugging then m_State.GetDriver()->UseDebugBreakProcess() should return false and then you won't hit line 1631, but line 1646.
Is this the case?

As far as I remember, I was able to hide the console window, back in then when I've implemented this feature.
Also I don't think there are any changes to the handling of remote debugging lately (last 6 months).

Lastly: If you have any patches, it might be good idea to show them, so we can try to integrate them in the official release.

--- End quote ---
Well, I must say, that this was my mistake here. :) I did not put the localhost:2331 in to the fields IP Address:... Port:... that is why plugin thought, that this is not remote target.
I did fill that fields with the info and now it works!
Thanks for that info!
Sorry one more time for that mistake.

I think, I can mark that thread as solved.

Navigation

[0] Message Index

[*] Previous page