Code::Blocks Forums
User forums => Help => Topic started by: bobinne13 on April 06, 2011, 07:24:23 pm
-
Hello
Sorry for my english but i don't use it everyday lol!
So! All's in the tittle!
I can't use correctly my debbuger.
When i clic on run to cursor my program don't stop at the cursor, i try F4 too but don't work.
breakpoints don't stop the debugger too. :(
I have C::B 10.05 on windows seven
mingw and gdb version 6.8
[-g] is enable in debug compiler setting ( first line ).
I post the logs if that tel you something :
Building to ensure sources are up-to-date
Build succeeded
Selecting target:
Debug
Adding source dir: C:\Users\Noël\Desktop\Pacmn Wndws\
Adding source dir: C:\Users\Noël\Desktop\Pacmn Wndws\
Adding file: bin\Debug\Pacmn Wndws.exe
Starting debugger:
done
Registered new type: wxString
Registered new type: STL String
Registered new type: STL Vector
Setting breakpoints
Debugger name and version: GNU gdb 6.8
Child process PID: 2164
Program exited normally.
Debugger finished with status 0
-
[-g] is enable in debug compiler setting ( first line ).
Make sure that:
[-s] is disabled
[-Ox] is disabled
...and inspect the full compiler log about the command line if you properly compile with debug symbols (see my sig how to do so...).
-
Also you can try newer gdb + debugger's nightly...
-
And use code-tags to paste
-
I get discourage... :(
I have another computer with exatly the same configuration, and the debbug work on it...
oBFusCATeD
I had try newer nightly like you suggest, but no results.
MortenMacfly
I had inspect the full compiler ( like you explain it in your sign, thanks !!) and I'm sure of my compiler setting, firstly because I just look at after your post ;) and beacause I have read that is the basic configuration after install C::B, could you confirm ?
jens
sorry for code-tags. ( I didn't now that logs is a code)
Befor became depressive I have uninstall C::B and flush registery, and install new time, but you now what ? No Change....
My next step is to uninstall windows and all programms but it's a extrem solution and I'm not really enthusiastic...
My new idea is that a programm make interference with my dbg, because it's the unic difference with my other pc, but I don't now witch is it in this case...
-
Is the path for your source files is the same on your 2 computers ?
regards, pasgui
-
Is the code source path for your source files is the same on your 2 computers ?
regards, pasgui
Yes i'ts the same. I had test another code most basic and sure on the two computer, to dismiss the possibility of error in the code that i'm working on... :).
-
Have you tried to debug your program with gdb directly?
Does it work?
-
Have you tried to debug your program with gdb directly?
Does it work?
I don't know do that, could you explain me please !
-
Type: "gdb tutorial" in your favorite search engine.
Also you can try to read the GDB's manual or RTFM! :lol:
-
Type: "gdb tutorial" in your favorite search engine.
Also you can try to read the GDB's manual or RTFM! :lol:
Lol sorry, i had no think to search in my "favorite engine". I'm going to do that :D
Just a new information :
U now what ? I just uninstall Windows and clean my 2 HDD (raid 0 ) and install new time ( I do that sometimes ( 2 times by year ) to clean all my system ) I just keep my work on another HDD . And this time the first thing that I had done were to install my favorite IDE and try my DBG and... nothing LOL !!! The problem is already here !!! As you can see i really try everything !!! :lol:
-
Hello everybody !!
I found the problem :D !!!!
The problem is my last name :evil: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!??????????????????????????????????????????????????????????????????????
Kof :(
My last name is "noël", and codeblocks can't support that !!!!! The two points on the "ë" can abort the debbug, it's crazy isn't it :shock:.
So i save my projects in another files who don't use my name.
Thanks a lot everybody !!! :D
-
Probably it is time to add a warning message if there are wrong characters (non ascii) in the paths...
-
yes probably!! :lol:
-
Probably it is time to add a warning message if there are wrong characters (non ascii) in the paths...
Yes, but only if it's a problem with the debugger itself, otherwise we should fix the path handling.
-
I have this problem too, few days ago check debugger on other computer and it worked there.
-
So you're using a path with strange characters and the debugger doesn't work or what?
No magic ball here, to tell what is wrong, I need some details :)
Have you tried to debug from the command line, have you tried to enable the debug log to see what commands are executed and what is their output?