X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
From:	Steve Waldo <steven DOT j DOT waldo AT seagate DOT com>
Subject:	Re: seg fault produces stackdump with no stack trace
Date:	Mon, 4 Aug 2008 12:49:29 +0000 (UTC)
Lines:	8
Message-ID:	<loom.20080804T124730-361@post.gmane.org>
References:	<loom DOT 20080801T151340-446 AT post DOT gmane DOT org> <loom DOT 20080801T174446-165 AT post DOT gmane DOT org> <20080801191550 DOT GA18883 AT ednor DOT casa DOT cgf DOT cx>
Mime-Version:	1.0
User-Agent:	Loom/3.14 (http://gmane.org/)
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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

Christopher Faylor writes:

> I just checked in a fix which should keep the stack trace going even
> when it finds a return address of zero.

That'll be great. Thanks much!

--Steve


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -