Code::Blocks Forums
Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: Mikhail on April 08, 2013, 04:16:21 am
-
Hi,
Let me make it clear:
Breakpoints which are set while program is running, are NOT reachable,
debugger does not break on them.
To reproduce the behavior start debugging, then set break
point (on menu handler or something like that).
Program will not break when you call this menu/
If break point is set before starting debugger or when debugger
is paused on some other break point, I can set new break point
and it is reachable.
Not all programs exhibit this.
My question is what possibly could cause this?
I use "-g" to enable debugging.
The program in question is too big to post.
Thank you,
Mikhail
-
Hi,
When I start debugging and then set break point then program breaks when this line
is reached. It does work and I had to compile example with wxWidgets to verify it.
However in my program (uses old wxwidgets) for some reason it does not happen -
when I start the program under debugger and set break point while running is never reached.
I can't understand your report, can you show us the exact steps to reproduce your bug?
BTW: Please edit your post, and wrap your log messages with code tags, thanks.
-
Also please redo the log that doesn't work after you've enabled full logging in the options of the debugger (Settings -> Debugger)
-
Using both: -g and -s would cause such behaviour and is a common mistake. Post the full build log for more...
-
Attached is compilation and debug logs.
I am not using "-s" option.
When I tried to set break point debugger posted message (see in the log)
[debug]Code::Blocks is trying to interrupt process with pid: 4020; child pid: 0 gdb pid: 4020
Continuing...
It seems that actual point was only set on exit
[debug]> break "/home/misha/tmp/wxxt-1.67/samples/demo/demo.cpp:353"
[debug]Breakpoint 2 at 0x804fb53: file /home/misha/tmp/wxxt-1.67/samples/demo/demo.cpp, line 353.
Your help is appreciated,
Thank you
Mikhail
[attachment deleted by admin]
-
The problem is that the pid detection failed...
-
What could be done on my side to find out why it is failed?
If I start program outside of CB and then attach debugger to it
everything works as expected.
-
What could be done on my side to find out why it is failed?
Nothing, I have to fix this bug.
-
Let me know if you need code from me. I can package GUI lib + demo program + CB workspace