I used the Dev-C++ debugger a lot last year.
This week, I started a new project with it, but when I set a breakpoint and try to run the debugger, it does not run. It begins by doing something that I can't see, because my video driver has a bug that makes it blank the screen out whenever Dev-C++ opens a console window. Then I press "alt-tab" to be able to see the screen again. I see the debugger open, with buttons highlighted like "Next step", "Step into", "Continue", and "Stop execution", indicating that the debugger is running. But no source code is displayed; pressing F7 (next step) does nothing; nothing I do has any visible effect, unless I choose "Stop execution", in which case it seems to stop execution.
Dev-C++ version 4.9.9.2
Windows XP SP2
Compile log: Unfortunately, although I can select the text of the compile log, I can't copy it. Perhaps this is another symptom of the problem.
An example line from it says
g++.exe -D__DEBUG__ -c main.cpp -o main.o -D__DEBUG -ansi -g3
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Answer: I installed Dev-Cpp with MinGW. Then I replaced my hard drive, installed Dev-Cpp without MinGW, and forgot that I had done so. Dev-Cpp did not know where to find gdb, I suppose. Uninstalling DevCpp, and installing the version with MinGW, put it back to how it was before.
The remaining question is: Why was it able to find Cygwin's gcc and use it to compile, but not able to find Cygwin's gdb (in same bin directory), and use it to debug?
A related question is: How can I set Dev-Cpp up to use Cygwin's gcc and gdb, instead of MinGW's? Adding the Cygwin binaries to the path lets Dev-Cpp find gcc, but not gdb. Specifying the locations of programs (including gcc and gdb) in Dev-Cpp's "compiler options" window appears not to work.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I used the Dev-C++ debugger a lot last year.
This week, I started a new project with it, but when I set a breakpoint and try to run the debugger, it does not run. It begins by doing something that I can't see, because my video driver has a bug that makes it blank the screen out whenever Dev-C++ opens a console window. Then I press "alt-tab" to be able to see the screen again. I see the debugger open, with buttons highlighted like "Next step", "Step into", "Continue", and "Stop execution", indicating that the debugger is running. But no source code is displayed; pressing F7 (next step) does nothing; nothing I do has any visible effect, unless I choose "Stop execution", in which case it seems to stop execution.
Dev-C++ version 4.9.9.2
Windows XP SP2
Compile log: Unfortunately, although I can select the text of the compile log, I can't copy it. Perhaps this is another symptom of the problem.
An example line from it says
g++.exe -D__DEBUG__ -c main.cpp -o main.o -D__DEBUG -ansi -g3
Answer: I installed Dev-Cpp with MinGW. Then I replaced my hard drive, installed Dev-Cpp without MinGW, and forgot that I had done so. Dev-Cpp did not know where to find gdb, I suppose. Uninstalling DevCpp, and installing the version with MinGW, put it back to how it was before.
The remaining question is: Why was it able to find Cygwin's gcc and use it to compile, but not able to find Cygwin's gdb (in same bin directory), and use it to debug?
A related question is: How can I set Dev-Cpp up to use Cygwin's gcc and gdb, instead of MinGW's? Adding the Cygwin binaries to the path lets Dev-Cpp find gcc, but not gdb. Specifying the locations of programs (including gcc and gdb) in Dev-Cpp's "compiler options" window appears not to work.
Sorry - Here is the compile log:
Compiler: Default compiler
Building Makefile: "C:\Phil\code\ai\collabFilter\code\src\Makefile.win"
Finding dependencies for file: C:\Phil\code\ai\collabFilter\code\src\main.cpp
Finding dependencies for file: C:\Phil\code\ai\collabFilter\code\src\sparse2D.cpp
Finding dependencies for file: C:\Phil\code\ai\collabFilter\code\src\fast2D.cpp
Finding dependencies for file: C:\Phil\code\ai\collabFilter\code\src\dense2D.cpp
Finding dependencies for file: C:\Phil\code\ai\collabFilter\code\src\rating.cpp
Finding dependencies for file: C:\Phil\code\ai\collabFilter\code\src\movie.cpp
Executing make...
make.exe -f "C:\Phil\code\ai\collabFilter\code\src\Makefile.win" all
g++.exe -D__DEBUG__ -c main.cpp -o main.o -D__DEBUG -ansi -g3
g++.exe -D__DEBUG__ -c movie.cpp -o movie.o -D__DEBUG -ansi -g3
g++.exe -D__DEBUG__ main.o sparse2D.o fast2D.o dense2D.o rating.o movie.o -o "..\bin\filter.exe" -g3
Execution terminated
Compilation successful
I solved the problem with the console window, using info on the web page
http://support.microsoft.com/kb/126031
Same symptoms. I can just see them better.
In the left "Debug" tab, sometimes pressing F7 makes a variable name appear. After the variable name, it always says "= Not found in current context"
It sounds like there is no debug information saved, but I think I'm giving the right parms to save it.