DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:reply-to:references:to:cc:from
	:message-id:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=Bd0xVK3/hBKyzjyP
	gkLjOy74vsj+8eoeGvIjy9CypEHFEDfbkyTDy3/Rzma2t0MwZb67BnrGzcVntPpj
	2ZzhkEYcm22dhMtn4SJ6zI5G5eGAdEZYOwZC+9g4ZKEEJhYvximwvBWZD/2VbL9K
	Ub9kPCOMExn5EX0tfzuw+suaNF0=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: Analyzing a SEG FAULT that gdb doesn't help with
Reply-To: cygwin@cygwin.com
References: <CAOC2fq_fahjLapKbgO8Xer8neEjv1Ohs4bM3JOWcka0ajjcbCg@mail.gmail.com> <55BA373A.4020909@dronecode.org.uk>
To: cygwin@cygwin.com
Cc: mike@kmcardiff.com
From: Jon TURNEY <jon.turney@dronecode.org.uk>
Message-ID: <55BB6F47.1000906@dronecode.org.uk>
Date: Fri, 31 Jul 2015 13:51:19 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <55BA373A.4020909@dronecode.org.uk>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

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