IMPORTANT!!! CODEBLOCKS VISUAL DEBUGGER IS BROKEN (FIX)

[devsh]

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).

[CuteAlien]

Guess I'm lucky for once that Debian stable uses old software. I remember same problem happened in the switch from gdb 6 to 7. Not sure if gdb as library works by now - back then it was still in the works I think and everyone parsed.

[chronologicaldot]

... or if you're on Linux Mint (due to the rolling release).

Glad I use Premake.

Thanks for the heads up.

[devsh]

Premake, that doesn't debug, does it?

[chronologicaldot]

No, so I use gcc messages, and I have a list of other tools I can use if I really want something.
I did try out CodeBlocks some time ago and was heartily disappointed with it for reasons I can't recall. Hearing that it's broken conjures up memories.

[REDDemon]

this fix a blue screen here .

[devsh]

gdb 7.11 seems to work fine