X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-3.6 required=5.0 	tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: sourceware.org
To: cygwin@cygwin.com
From: Eric Blake <ebb9@byu.net>
Subject:  Re: perl threads on 2008 R2 64bit = crash ( was: perl 5.10 threads  on 1.5.25 = instant crash )
Date: Fri, 17 Jul 2009 16:22:01 +0000 (UTC)
Lines: 23
Message-ID:  <loom.20090717T161628-634@post.gmane.org>
References:  <4A5E3F1F.9040103@gmail.com>  <20090716161219.GP27613@calimero.vinschen.de>  <4A5F59A1.1060902@gmail.com>  <20090716195552.GU27613@calimero.vinschen.de>  <20090716211823.GC22617@ednor.casa.cgf.cx>  <20090717085727.GW27613@calimero.vinschen.de>  <4A607EE5.5050306@gmail.com>  <20090717134114.GX27613@calimero.vinschen.de>  <4A608954.4040301@gmail.com>  <20090717152920.GY27613@calimero.vinschen.de> <20090717154431.GA31572@ednor.casa.cgf.cx>
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@cygwin.com; run by ezmlm
List-Id: <cygwin.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

Christopher Faylor <cgf-use-the-mailinglist-please <at> cygwin.com> writes:

> Right, and I don't know how you could make the claim that Cygwin apps
> don't install SEH handlers.  We can't possibly know how every Cygwin app
> does this.  Obviously there's at least one app out there which has
> decided that it needs to use Windows-specific methods to accomplish a
> goal.  I'm not exactly thrilled to see code which has decided to dig
> deep into Windows internals.  That's what Cygwin is supposed to prevent.

If cygwin were to provide a working sigaltstack, then libsigsegv would be able 
to use that instead of digging into Windows internals (because that's the 
interface that libsigsegv expects to be able to use on Linux).  Until that 
point, at least all clients of libsigsegv are messing with Windows handlers; 
but at least libsigsegv is small and self-contained enough to track potential 
portability problems if cygwin makes changes in this area.  On the other hand, 
even patching things to allow libsigsegv to use standardized interfaces won't 
help apps like perl if they are doing SEH manipulations without the use of 
libsigsegv.

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