Code::Blocks Forums

Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: rickg22 on January 18, 2006, 12:14:29 am

Title: How to interrupt C::B hangs (infinite loops) with GDB?
Post by: rickg22 on January 18, 2006, 12:14:29 am

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

Title: Re: How to interrupt C::B hangs (infinite loops) with GDB?
Post by: takeshimiya on January 18, 2006, 12:25:10 am

I have the same problems with gdb.

Title: Re: How to interrupt C::B hangs (infinite loops) with GDB?
Post by: TDragon on January 18, 2006, 12:44:56 am

Ctrl+C?
Not that it'd necessarily be much more helpful...

Title: Re: How to interrupt C::B hangs (infinite loops) with GDB?
Post by: rickg22 on January 18, 2006, 01:10:02 am

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

Title: Re: How to interrupt C::B hangs (infinite loops) with GDB?
Post by: 280Z28 on January 18, 2006, 02:11:37 am

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).

Title: Re: How to interrupt C::B hangs (infinite loops) with GDB?
Post by: rickg22 on January 18, 2006, 03:29:46 am

:-o THANKS A LOT! :D

Title: Re: How to interrupt C::B hangs (infinite loops) with GDB?
Post by: Game_Ender on January 18, 2006, 05:47:24 am

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.