Help! Can't run Dev-C++ 5.0 debugger

[ccobra75]

Hello,

I'm having a problem running Dev-C++ 5.0 beta 9.2 (4.9.9.2)with Mingw/GCC debugger.
I'm running Xp and I downloaded installation instructions from:

http://online.mq.edu.au/pub/COMP125/support/bloodshed_guide.pdf

There are two examples of how to set up the compiler options which is
confusing so I tried both - no results. I followed these instructions to the letter.
When I start debug, I noticed the bar/line does not turn Blue as in the picture nor does the Project1.exe window open (pg 27). Can someone look at these instructions and let me know if a step is missing.

thanks,
Briant

[ccobra75]

Thanks for not toasting my buns. I did read the "PRBPA question" however, since there were "no issues"
compiling, I did not add the text below. Looking at it now made me realize why it's required. I'm a
rookie (obviously).

{Compiler: Default compiler
Building Makefile: "C:\Z_Projects\PROJECTs\DevCpp\DevC++4992\Makefile.win"
Executing make...
make.exe -f "C:\Z_Projects\PROJECTs\DevCpp\DevC++4992\Makefile.win" all
g++.exe main.o -o "Project1.exe" -L"C:/Dev-Cpp/lib" -ggdb

Execution terminated
Compilation successful}

I'll try both of your suggestions and stick with what's comfortable in terms of usability.

Briant

[cpns]

Because the compilation of main.cpp was already up-to-date, your log only shows the linker invocation. The log should generally be that from a "Rebuild-all" to ensure in contains complete information.

I think Dev-C++ applies -g3 rather than -ggdb, but it is essentially the same thing.

Clifford

[cpns]

Apparently for some people the debugger works. I have not been able to make it work for a long time. This did not worry me too much because frankly, even when it does work, it sucks.

I took a quick look at Ian Cowell's instructions, and I am not sure why he adds the -g option, then tells you to select "No" for "Generate debugging information". Selecting "Yes" in fact adds teh -g option!

However, you should note that the "Tools->Compiler options" settings are applied to files compiled and linked without a project (a bad idea IMO), and are used as initial settings for projects. If you have a project already, changing these settings (apart from the ones on the "Tools->Compiler options->Compiler tab") has no affect on the project itself. That is probably why Mr Cowell has suggested using the -g option explicitly - because he did not understand that.

Anyhow, you should always post the "Compile Log" - from that we can tell if you have configured the project correctly. This point is made very clear in the "PLEASE READ BEFORE POSTING A QUESTION" thread. You read that already right!? Also in that thread are instructions for using the debugger - you might take a look since you are essentially asking teh forum to repeat what is already provided there. The less tolerant would flame you, but since I believe that teh debugger is not worth the effort, on this subject I am less concerned.

If you too decide that it is not usable, consider the MinGW Insight debugger (www.mingw.org). It can be loosely integrated with Dev-C++ via the Tools menu customization feature. You will still need all the same compiler/linker settings to build with debug information in the code.

If that still does not satisfy VC++ 2005 Express Edition (or even 2008 now) has a debugger second to none. Since I believe that the debugger is the most important tool a programmer needs after the compiler, I have no reservations in suggesting a 'competitor' tool if this one does not do the job for you.

Clifford