X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
In-Reply-To:	<20090724182112.GB15507@ednor.casa.cgf.cx>
References:	<4A678AC7 DOT 7090303 AT x-ray DOT at> <20090723144038 DOT GA11519 AT ednor DOT casa DOT cgf DOT cx> <loom DOT 20090723T145926-237 AT post DOT gmane DOT org> <20090723171656 DOT GA6973 AT ednor DOT casa DOT cgf DOT cx> <4A690D27 DOT 3050109 AT gmail DOT com> <20090724020225 DOT GB10306 AT ednor DOT casa DOT cgf DOT cx> <4A6924E7 DOT 9030103 AT gmail DOT com> <20090724043005 DOT GA10827 AT ednor DOT casa DOT cgf DOT cx> <6910a60907241054h6bebc6eo279180a0a9fd21b AT mail DOT gmail DOT com> <20090724182112 DOT GB15507 AT ednor DOT casa DOT cgf DOT cx>
Date:	Fri, 24 Jul 2009 21:10:52 +0200
Message-ID:	<6910a60907241210s680e7887j6f5c9eca31f74b45@mail.gmail.com>
Subject:	Re: [1.7] Updated: libsigsegv-2.6-1
From:	Reini Urban <rurban AT x-ray DOT at>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
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

2009/7/24 Christopher Faylor:
> On Fri, Jul 24, 2009 at 07:54:50PM +0200, Reini Urban wrote:
>>But segv handling is mandatory for decent performance and only
>>stack overflow handling corrupts the cygwin stack.
>
> I can't grok that sentence. =A0Are you reporting a bug?

Sorry, I understood that wrong.
I thought Eric reported the bug that installing the libsigsegv *stack
overflow* handler
corrupted the cygwin SEH chain with Win2008. Not the *segv* handler.

But then I learned that indeed a Win2008 exception causes another SEGV
to be delayed (http://lists.gnu.org/archive/html/bug-gnulib/2009-07/msg0009=
2.html)
and this fools the segv handler, not the stack handler.
--=20
Reini Urban
http://phpwiki.org/           http://murbreak.at/

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