Code::Blocks Forums

User forums => Help => Topic started by: Calmarius on November 30, 2015, 08:40:34 am

Title: Code::Blocks doesn't recognize that the debugger is stopped
Post by: Calmarius on November 30, 2015, 08:40:34 am

I'm working on 64 bit Ubuntu, and I'm using C::B 13.12

The gdb -v output is:

GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.launchpad.net/gdb-linaro/>.


If I set a breakpoint, the program stops but the IDE still thinks it's running and not giving me call stack or anything. Also no way to continue the program since the IDE thinks it's running.

When an assert fail occurs and the program gets SIGABRT, the IDE just exits the debugger and does not show lines or call stack.

The project was created by the "Empty project" wizard.

Something is really screwed up... Any ideas...

Title: Re: Code::Blocks doesn't recognize that the debugger is stopped
Post by: oBFusCATed on November 30, 2015, 08:47:35 am

Can you enable the full log of the debugger and post it here for inspection?

Title: Re: Code::Blocks doesn't recognize that the debugger is stopped
Post by: Calmarius on December 04, 2015, 10:07:14 pm

Later I discovered that this weird behavior is caused by the fact that I updated my compiler to gcc 4.81 which uses a differrent format for debug symbols which is not recognized correctly by gdb, while you can set breakpoints on lines, it doesn't show line, when the gdb stops. So I needed to update gdb too. Now it works.

Title: Re: Code::Blocks doesn't recognize that the debugger is stopped
Post by: oBFusCATed on December 05, 2015, 02:27:31 am

Good to know it is working now.  8)