X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-3.5 required=5.0 	tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Eric Blake <ebb9 AT byu DOT net>
Subject:  Re: libsigsegv error handling
Date: Wed, 22 Jul 2009 17:23:58 +0000 (UTC)
Lines: 24
Message-ID:  <loom.20090722T171349-590@post.gmane.org>
References:  <20090715185636 DOT GA16211 AT ednor DOT casa DOT cgf DOT cx> 	 <4A5F59A1 DOT 1060902 AT gmail DOT com> 	 <20090716195552 DOT GU27613 AT calimero DOT vinschen DOT de> 	 <20090716211823 DOT GC22617 AT ednor DOT casa DOT cgf DOT cx> 	 <20090717085727 DOT GW27613 AT calimero DOT vinschen DOT de> 	 <4A607EE5 DOT 5050306 AT gmail DOT com> 	 <20090717134114 DOT GX27613 AT calimero DOT vinschen DOT de> 	 <loom DOT 20090717T140900-805 AT post DOT gmane DOT org> <4A608C72 DOT 2010504 AT gmail DOT com> 	 <loom DOT 20090717T144655-62 AT post DOT gmane DOT org> <6910a60907220124p1e4fed27kc82869cad4b0f88b AT mail DOT gmail DOT com> <4A66F783 DOT 1070503 AT byu DOT net>
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
Content-Transfer-Encoding:  7bit
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

Eric Blake <ebb9 <at> byu.net> writes:

> >> Is there a chance that this represents a bug in
> >> libsigsegv SEH handling that needs to be reported upstream?
> > 
> > I'll report that, if it turns out so.
> 
> I've already mentioned it to Bruno, and am still working on a fix.

FWIW, rebuilding m4 1.4.13 picks up the new libsigsegv0 dll, but it still 
exhibits the crash when used under cygwin-1.7.0-51 (ie. the bug is not whether 
libsigsegv was linked in static or dynamic, but that libsigsegv is over-eager 
to claim that all SEH faults should be handled like SEGV faults).  The 
particular m4 crash is gone with cygwin1.dll built today (thanks to my recent 
newlib fflush patch).  Meanwhile, I will be packaging m4-1.4.13-2 to pick up 
the new libsigsegv0 (so that when Bruno does fix libsigsegv, I don't have to 
rebuild m4-1.4.13-3 to relink against the fix), and that will also include a 
one-liner patch (currently in m4.git) that makes the particular m4 crash go 
away even if you don't have a self-built cygwin1.dll.

-- 
Eric Blake




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