X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By:	sourceware.org
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX1/Qxv271gzWVmf1ZRwNUWdn
Date:	Sat, 9 Mar 2013 17:02:22 -0500
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: emacs-X11 crashes under gdb in recent snapshots
Message-ID:	<20130309220222.GB7961@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<5137B57A DOT 2020204 AT cornell DOT edu> <20130307054426 DOT GB8145 AT ednor DOT casa DOT cgf DOT cx> <20130307064921 DOT GA2424 AT ednor DOT casa DOT cgf DOT cx> <20130308163430 DOT GA814 AT ednor DOT casa DOT cgf DOT cx>
MIME-Version:	1.0
In-Reply-To:	<20130308163430.GA814@ednor.casa.cgf.cx>
User-Agent:	Mutt/1.5.20 (2009-06-14)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On Fri, Mar 08, 2013 at 11:34:30AM -0500, Christopher Faylor wrote:
>On Thu, Mar 07, 2013 at 01:49:21AM -0500, Christopher Faylor wrote:
>>On Thu, Mar 07, 2013 at 12:44:26AM -0500, Christopher Faylor wrote:
>>>On Wed, Mar 06, 2013 at 04:30:34PM -0500, Ken Brown wrote:
>>>>Starting with the 20130102 snapshot, I get a SEGV if I run emacs-X11 
>>>>under gdb.
>>>
>>>Thanks for the explicit instructions.
>>>
>>>I can reproduce this.  Investigating.
>>
>>I see what the problem is but it's too late to fix it now.
>>
>>So, instead, I will go to bed and obsess and dream about it instead.
>>
>>I will fix it tomorrow, though.
>
>Or not.  RL intervened.  Still checking.  It's trickier to fix than
>I thought.

This should be fixed now.  You'll need the new just-released gdb and
the upcoming snapshot for this to work correctly.

Changes in gdb and cygwin1.dll should now allow gdb to recognize
Cygwin-specific signals.  That's something that I've wanted to do for
more than ten years.  I startled my wife with my whoop! when gdb
reported a "SIGTERM" at the correct line in my source code.

This behavior is still experimental and likely to need some more
tweaking but, boy, this was a long time coming.

cgf

--
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

- Raw text -