News:

As usual while waiting for the next release - don't forget to check the nightly builds in the forum.

Main Menu

How to interrupt C::B hangs (infinite loops) with GDB?

Started by rickg22, January 18, 2006, 12:14:29 AM

Previous topic - Next topic

rickg22

Does anybody know? Because if i press ctrl-break, the whole gdb process (and not just C::B) gets interrupted :(

takeshimiya


TDragon

Ctrl+C?
Not that it'd necessarily be much more helpful...
[url="https://jmeubank.github.io/tdm-gcc/"]https://jmeubank.github.io/tdm-gcc/[/url] - TDM-GCC compiler suite for Windows (GCC 9.2.0 2020-03-08, 32/64-bit, no extra DLLs)

rickg22

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? :?

280Z28

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).
78 280Z, "a few bolt-ons" - 12.71@109.04
99 Trans Am, "Daily Driver" - 525rwhp/475rwtq
Check out The Sam Zone :cool:

rickg22


Game_Ender

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.