|
From: Chris J. <cj...@cy...> - 2003-10-25 23:10:37
|
Duncan Murdoch wrote: > Is there a simple function or macro to put into code to trap to the > debugger (using Insight on top of gdb)? > Which Insight ? > I've tried DebugBreak (a windows.h function), but it traps first > somewhere in the Windows library, and I need to single step to get > into my own code. I'd like Insight to stop right on the source line > that asked for the trap. > The DebugBreak should have worked. Maybe GDB just continued. I had some code that generated a STATUS_BAD_STACK type exception. When run from cmd the program stopped when the exception occurred. When run in GDB it and GDB hung (no ^C support). Looking into GDB I found the GDB exception handling loop considered the exception unknown and continued, which resulted the app generating the same exception again. Maybe unknown exceptions should stop GDB. I do not know enough about Windows exceptions (SEH) to make this decision. -- Chris Johns, cjohns at cybertec . com . au |