IMPORTANT!!! CODEBLOCKS VISUAL DEBUGGER IS BROKEN (FIX)
Posted: Fri Jul 24, 2015 6:09 pm
This issue mostly affects Linux, unless you've updated your mingw on windows or performed a similar update on Mac
The issue came to my attention when I was using the latest CodeBlocks (13.12)
The problem is that CodeBlocks uses parsing of the GDB output to recover the debugging information, rather than using GDB properly (in the form of a library - a static library even better!).
Now between version 7.7 and 7.9 the output of GDB has changed slightly and now codeblocks is unable to pickup the PID of the debugged application and this results in being unable to stop the debugger, or break/pause (it simply says "No stack.").
If you downgrade to gdb 7.7 then there is no problem whatsoever.
You'll notice this issue if you upgrade from Ubuntu 14.04 or if you're on Linux Mint (due to the rolling release).
The issue came to my attention when I was using the latest CodeBlocks (13.12)
The problem is that CodeBlocks uses parsing of the GDB output to recover the debugging information, rather than using GDB properly (in the form of a library - a static library even better!).
Now between version 7.7 and 7.9 the output of GDB has changed slightly and now codeblocks is unable to pickup the PID of the debugged application and this results in being unable to stop the debugger, or break/pause (it simply says "No stack.").
If you downgrade to gdb 7.7 then there is no problem whatsoever.
You'll notice this issue if you upgrade from Ubuntu 14.04 or if you're on Linux Mint (due to the rolling release).