Re: Gdb and stopping at assert or segmentation faults

Hi all Dave Korn dave.korn at artimi.com writes: Anyway, break __assert works for catching the assertions. Dunno what's up with the SEGVs. well, it turns out Dave's suggestion doesn't work anymore on latest cygwin (tested this only with C++ programs): GNU gdb

Re: Gdb and stopping at assert or segmentation faults

Dave Korn dave.korn at artimi.com writes: Anyway, break __assert works for catching the assertions. Dunno what's up with the SEGVs. Hi Dave I thought this would break even when the assertion didn't fail, but I was wrong there! Good suggestion! Thanks Kris -- Unsubscribe info:

Gdb and stopping at assert or segmentation faults

Hi 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

Re: Gdb and stopping at assert or segmentation faults

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

RE: Gdb and stopping at assert or segmentation faults

Hi Brian 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 crash? Ok. However, what I was saying is that I would like to be able to backtrace when I launch

RE: Gdb and stopping at assert or segmentation faults

Original Message From: Kris Thielemans Sent: 29 June 2005 17:24 However, what I was saying is that I would like to be able to backtrace when I launch a program from within gdb: Gdb myprog Run assert or segmentation fault Info stack Odd, I would have thought this should work.