User forums > Using Code::Blocks
Debugger issues
oBFusCATed:
Hello, I have some questions/problems about debugging with code::blocks:
1. Why it is not possible to set breakpoints when the debugger is started?
2. Is it possible to continue the program at different point? I found that gdb can do it here: http://sourceware.org/gdb/current/onlinedocs/gdb_15.html#SEC147
Have these been implemented or planned for implementation in near future? If not how hard will it be for a newbie(me) in c::b development to implement them?
3. When I make a change to the code and hit "debug start" button, c::b locks with 100% cpu usage and have to kill it :lol:
I'm using svn build (I don't remeber when updated, but it was soon enough) under gentoo 64bit linux (I think on win32 the behaviour was the same).
Pecan:
//-- Debugging
Debugging with CodeBlocks
See the debugging sections of the following:
http://www.sci.brooklyn.cuny.edu/~goetz/codeblocks/
http://www.sci.brooklyn.cuny.edu/~goetz/codeblocks/codeblocks-instructions.pdf
MortenMacFly:
--- Quote from: oBFusCATed on March 28, 2007, 12:49:26 pm ---3. When I make a change to the code and hit "debug start" button, c::b locks with 100% cpu usage and have to kill it :lol:
--- End quote ---
Cannot reproduce. Do you have a minimalistic project to demonstrate and a more detailed step-by-step instruction?
With regards, Morten.
mike__t:
I've run into this problem with a cross-platform project that has backtick expressions for various settings, e.g. `wx-config --libs`. Under Windows, these are evaluated ok during a normal build, but for some it hangs when the build is launched by a request to start the debugger.
I traced it far enough to see that it appears the launched command process never completes, but once I saw what was going on, I used the handy new platform feature to mark this target for Unix only. (Our Windows target only uses path names.)
oBFusCATed:
--- Quote from: mike__t on March 28, 2007, 07:45:38 pm ---I've run into this problem with a cross-platform project that has backtick expressions for various settings, e.g. `wx-config --libs`. Under Windows, these are evaluated ok during a normal build, but for some it hangs when the build is launched by a request to start the debugger.
I traced it far enough to see that it appears the launched command process never completes, but once I saw what was going on, I used the handy new platform feature to mark this target for Unix only. (Our Windows target only uses path names.)
--- End quote ---
Hm, may be the crashes were on windows. I've just tested on linux and there is no problem, it runs ok.
My project is SDL project, so I use `sdl-config --cflags`. Thanks for the enlightening :)
--- Quote from: oBFusCATed on March 28, 2007, 12:49:26 pm ---1. Why it is not possible to set breakpoints when the debugger is started?
--- End quote ---
Okay, I should have given more info on this here. But I was at work, so there was no code::blocks to refresh my memory :oops:
So, the real problem is that I can't set breakpoint when the application is running (to make it stop), only when it is stopped on a breakpoint, then I can set/unset what ever I want.
Is is possible to be implement this feature?
Thank you for your responses, and keep up the good work :wink:
Navigation
[0] Message Index
[#] Next page
Go to full version