Re: Gdb and stopping at assert or segmentation faults

[Brian Dessent <brian at dessent dot net>]

Kris Thielemans wrote:

> I need to debug a program that throws up an assert(). On Linux, I'm used to
> be able to run the program in gdb, and when the assert happens, the program
> stops (in the assert function) and I can do a back trace (e.g. info stack).
> On cygwin on the other hand, I just get the assert message, and then gdb
> says "Program exited normally". No backtrace possible.
> 
> The same difference in behaviour between Linux and cygwin with segmentation
> faults. It would be incredibly useful to be able to see where the
> segmentation fault happened after the crash.

You need to set the 'error_start' parameter of the CYGWIN environment
variable to the (windows) path of gdb.

You can also call cygwin_internal (CW_DEBUG_SELF,
"c:\\path\\to\\gdb.exe") in your code to force a fault.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/