Does anybody know? Because if i press ctrl-break, the whole gdb process (and not just C::B) gets interrupted :(
I have the same problems with gdb.
Ctrl+C?
Not that it'd necessarily be much more helpful...
In these C::B forums i've read of some users reporting hangs (not crashes), and giving us the backtrace. How could they do it? :?
I use SysInternals Process Explorer. It can give a backtrace while the program is running. Ideally you could send a sigtrap to the program but I don't know how to do that (in windows).
:-o THANKS A LOT! :D
Those users were probably on Linux :), I start up gdb with the codeblocks exectuable (ie: gdb <cbdir>/codeblocks) then once gdb starts up I type run at the gdb command line. Ctrl+C just brings you back to the gdb command line, from there you can backtrace.