Code::Blocks Forums
User forums => Help => Topic started by: the-moon on November 18, 2005, 08:17:23 am
-
I'm trying to debug my C++ app, mingw32 for the complier.
But I'm having some trouble....
I try to debug and it says "Debugger executable not set. To set it, goto " etc
So, i goto project properties, then i goto "Projects build options"
I select "Produce Debugging Symbols"
After that i rebuild my project and try to debug again. And it tells me the same error again.
Could anyone please explain to me what I'm doing wrong....
-
Go to Settings -> Compiler, tab "Programs". Debugger should be set to gdb.exe
-
Yeah its set to gdb.exe.
-
Yeah its set to gdb.exe.
Did you veryify that you actually have a gdb.exe in the path? Are you using the Code::Blocks MinGW version? If not and you've donwloaded the MinGW package from somewhere else the debugger might be really missing.
Morten.
-
Did you veryify that you actually have a gdb.exe in the path? Are you using the Code::Blocks MinGW version? If not and you've donwloaded the MinGW package from somewhere else the debugger might be really missing.
Morten.
Yes gdb.exe is in my bin folder for codeblocks and yes i downloaded codeblocks Mingw version.
-
Can anyone please help me.
I really would like to do some coding today.
I dont want to have to reinstall Devc++. Id much rather use codeblocks. But if the codeblocks debugger dosent work, i have no choice but to use devc++ until its fixed.
-
Can anyone please help me.
Ok, let's do some basics:
1.) Could you verify that your PATH environment variable is setup in a way that there is
a) not another (incompatible) gdb.exe int the PATH
b) the real gdb.exe from code::Blocks ist IN the path
If not, just expand the PATH environment for testing purposes to the CodeBlocks\Bin directory. C::B will recoginise this after a restart of the application. Make sure you use the "My workplace" dialog to update the new PATH environment variable. otherwise the settings might not applied (or only after a restart).
2.) Please make sure you did not install C::B in a path that contains spaces. This might be an issue.
3.) Could you post a screenshot of the compiler (path) settings (global / project wise). Did you enable the Debugger's debug-log (within the settings of C::B GDB debugger). What's the output there?
Morten.
-
Can anyone please help me.
Ok, let's do some basics:
1.) Could you verify that your PATH environment variable is setup in a way that there is
a) not another (incompatible) gdb.exe int the PATH
b) the real gdb.exe from code::Blocks ist IN the path
If not, just expand the PATH environment for testing purposes to the CodeBlocks\Bin directory. C::B will recoginise this after a restart of the application. Make sure you use the "My workplace" dialog to update the new PATH environment variable. otherwise the settings might not applied (or only after a restart).
2.) Please make sure you did not install C::B in a path that contains spaces. This might be an issue.
3.) Could you post a screenshot of the compiler (path) settings (global / project wise). Did you enable the Debugger's debug-log (within the settings of C::B GDB debugger). What's the output there?
Morten.
Are u talking about my system Path?
Or a path for code::blocks...
System Enviroment Path -%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\CodeBlocks\bin
Heres a image of the paths for C::B, and also the error i get when i try and debug....
http://cdfbr.zidev.com/gfx/CBPath.jpg
^is this what u wanted?
Additional paths has nothing in it.
-
System Enviroment Path -%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\CodeBlocks\bin
http://cdfbr.zidev.com/gfx/CBPath.jpg
What wonders me: You are writing the path contains "C:\CodeBlocks\bin" but the screenshot states "C:\Program Files\Codeblocks". What is right?
Morten.
-
LoL
OMg....
It works!
I never even thought about that, i figured that code blocks would use the path i installed it from.
THanks alot for the help
-
It works!
Great! Then I can go to bed now... :lol:
Morten.
-
I never even thought about that, i figured that code blocks would use the path i installed it from.
Codeblocks? Yes!
Mingw? No!
Anyway here's a little tutorial on how MS-DOS works.
Once upon a time... :lol: there was something called command.com. Whenever you ran a program that wasn't in the current directory, it said "bad command or filename". So then someone got the idea of making a PATH variable, so that any paths inside it would run automatically. Many programs of MS-DOS like "find", "more" grew dependent on this feature to work correctly.
MinGW is not a "program" either. It's a set of independent programs that also depend on this PATH feature to work correctly.
See? It's no magic, you just have to know how these things work.
-
LoL
OMg....
It works!
I never even thought about that, i figured that code blocks would use the path i installed it from.
THanks alot for the help
I ment to say, i figured C::B would use the path i installed it to.
-
See? It's no magic, you just have to know how these things work.
rick22, didn't you advise me in another thread (http://forums.codeblocks.org/index.php/topic,1388.0.html) not to scare "newbies" like that...?! :lol: (Don't take it seriously, "the-moon".)
Morten.
...not yet in bed.