This is the mail archive of the
mailing list for the Cygwin project.
Re: Analyzing a SEG FAULT that gdb doesn't help with
- From: Jon TURNEY <jon dot turney at dronecode dot org dot uk>
- To: cygwin at cygwin dot com
- Cc: mike at kmcardiff dot com
- Date: Fri, 31 Jul 2015 13:51:19 +0100
- Subject: Re: Analyzing a SEG FAULT that gdb doesn't help with
- Authentication-results: sourceware.org; auth=none
- References: <CAOC2fq_fahjLapKbgO8Xer8neEjv1Ohs4bM3JOWcka0ajjcbCg at mail dot gmail dot com> <55BA373A dot 4020909 at dronecode dot org dot uk>
- Reply-to: cygwin at cygwin dot com
On 30/07/2015 15:39, Jon TURNEY wrote:
On 30/07/2015 00:16, Michael Enright wrote:
1) Why is it not the case that gdb handles this SEGV in the usual
manner? It too just allows the stackdump to be made and lets me know
that the inferior has run its course.
This shouldn't happen. Are you sure the crashing process is the direct
inferior of gdb, and not some wrapper process which runs it?
(uninstalled libtool generated binaries do this, for e.g.)
Oh, I just remembered something :)
I think you need to use the gdb command 'set cygwin-exceptions on' to
tell gdb to break on exceptions inside the cygwin DLL (by default they
are ignored, as they may be generated during normal operation when
checking a pointer is valid)
I shall have to see if I can find a place for these last couple of
answers in the FAQ or documentation somewhere. It's rather too obscure
at the moment.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple