Code::Blocks Forums
User forums => Help => Topic started by: Alexis on January 25, 2013, 02:20:33 pm
-
Sometimes, the debugger used "natively" by C::B (gdb) blocks.
I mean that I can't leave the debug mode inside C::B.
I'm obliged to kill gdb with a "killall -9 gdb" to get back to the "normal" perspective.
I saw this behavior with UI-based applications only, not with console applications.
Somebody, an idea where it does come from and about a way to fix this?
I'm running Linux Ubuntu 12.10, and I'm using C::B 12.11 (rev 8629).
Thanks.
-
Can you provide the full debugger's log (you have to enable it in Settings -> Debugger), when this thing happens?
Most of the time this happens because of a bug in our gdb-output-parser.
-
Can you provide the full debugger's log (you have to enable it in Settings -> Debugger), when this thing happens?
Most of the time this happens because of a bug in our gdb-output-parser.
OK, I see. Thanks.
I'll provide you with a gdb's log next time it happens.
-
Hi,
I have something like this:
[debug]Child process (pid:7454) doesn't exists
[debug]Code::Blocks is trying to interrupt process with pid: 7440; child pid: 7454 gdb pid: 7440
[debug]Quit
[debug]>>>>>>cb_gdb:
Each time, I try to stop debugger inside C::B, the message above is issued again and again.
I have to kill gdb to stop this.
Any idea?
-
This is expected in this situation, but doesn't help much, post the full log.