X-Recipient: archive-cygwin@delorie.com
X-Spam-Check-By: sourceware.org
Date: Fri, 24 Jul 2009 15:16:49 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [1.7] Updated: libsigsegv-2.6-1
Message-ID: <20090724191649.GA15948@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <20090723144038.GA11519@ednor.casa.cgf.cx>  <loom.20090723T145926-237@post.gmane.org>  <20090723171656.GA6973@ednor.casa.cgf.cx>  <4A690D27.3050109@gmail.com>  <20090724020225.GB10306@ednor.casa.cgf.cx>  <4A6924E7.9030103@gmail.com>  <20090724043005.GA10827@ednor.casa.cgf.cx>  <6910a60907241054h6bebc6eo279180a0a9fd21b@mail.gmail.com>  <20090724182112.GB15507@ednor.casa.cgf.cx>  <6910a60907241210s680e7887j6f5c9eca31f74b45@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6910a60907241210s680e7887j6f5c9eca31f74b45@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Fri, Jul 24, 2009 at 09:10:52PM +0200, Reini Urban wrote:
>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. ?Are 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/msg00092.html)
>and this fools the segv handler, not the stack handler.

Thanks for the clarification.

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

