From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin@cygwin.com
Cc: mike@kmcardiff.com
Subject: Re: Analyzing a SEG FAULT that gdb doesn't help with
Date: Fri, 31 Jul 2015 12:51:00 -0000 [thread overview]
Message-ID: <55BB6F47.1000906@dronecode.org.uk> (raw)
In-Reply-To: <55BA373A.4020909@dronecode.org.uk>
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
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2015-07-31 12:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 23:16 Michael Enright
2015-07-30 14:40 ` Jon TURNEY
2015-07-30 17:46 ` Michael Enright
2015-07-30 18:48 ` Michael Enright
2015-07-31 12:51 ` Jon TURNEY [this message]
2015-07-31 18:46 ` Michael Enright
2015-07-31 20:12 ` Michael Enright
2015-08-01 20:28 ` Brian Inglis
2015-08-02 1:55 ` Michael Enright
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55BB6F47.1000906@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=mike@kmcardiff.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).