Gdb and stopping at assert or segmentation faults
Wed Jun 29 19:06:00 GMT 2005
> You need to set the 'error_start' parameter of the CYGWIN
> environment variable to the (windows) path of gdb.
I think what you're saying is that if I do this, it will launch gdb on the
However, what I was saying is that I would like to be able to backtrace when
I launch a program from within gdb:
<assert or segmentation fault>
> You can also call cygwin_internal (CW_DEBUG_SELF,
> "c:\\path\\to\\gdb.exe") in your code to force a fault.
Ok. That's useful as well. Thanks!
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
More information about the Cygwin