For many months now I have been tracking CodeBlocks' development. I like almost everything about it, but I still can't use it for the following reason: Debugging doesn't seem to work on my Linux systems. Linux systems being 2 versions of Ubuntu, Debian Etch, and Fedora Core 6. On Ubuntu I used Gnome, on the others its KDE. The symptom is the same on all.
First, I download the head of the svn repository, build and install CodeBlocks. My installation is done to a directory that I own, so I don't need "root" to install. (I set the prefix= appropriately when configuring)
Build a simple C or C++ program with GCC including the -g option for debugging symbols. Builds fine.
Go to Debug menu and say Start. Some lines in the console output say that the debugger has started and the menu items for next, etc. are enabled. Nothing happens in the edit window. I would expect a highlighted line somewhere near the beginning of main().
Clicking on "Next Line" button in the toolbar or selecting that in the menu produces no output anywhere. All I can do is select or click on "Continue" and the program terminates "normally", and the debugger ends.
Because of this situation, I currently use jEdit to write code, commandline and makefiles to build, and kdbg (a debugger using the KDE desktop) to debug it. Sometimes I use Eclipse for larger projects. I'd really like to use CodeBlocks, but I want that debugging ability; it's how I verify that the code is doing what I want.
This issue was mentioned somewhere around svn version 1940, I believe. From what I read, it sounded like it would be addressed soon. So every once in a while, I update my code from the repository, rebuild Codeblocks and check debugging. Still the same. Its been a long time now so this time I thought I'd write and see if someone knows the story. Surely somebody uses CodeBlocks and does debugging on Linux successfully. Am I doing something wrong or am I not doing something I should?