X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Fri, 17 Jul 2009 18:36:16 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: perl threads on 2008 R2 64bit = crash ( was: perl 5.10 threads 	on 1.5.25 = instant crash )
Message-ID: <20090717163616.GZ27613@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20090716161219 DOT GP27613 AT calimero DOT vinschen DOT de> <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> <4A608954 DOT 4040301 AT gmail DOT com> <20090717152920 DOT GY27613 AT calimero DOT vinschen DOT de> <20090717154431 DOT GA31572 AT ednor DOT casa DOT cgf DOT cx>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20090717154431.GA31572@ednor.casa.cgf.cx>
User-Agent: Mutt/1.5.19 (2009-02-20)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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

On Jul 17 11:44, Christopher Faylor wrote:
> On Fri, Jul 17, 2009 at 05:29:20PM +0200, Corinna Vinschen wrote:
> >On Jul 17 15:23, Dave Korn wrote:
> >> Corinna Vinschen wrote:
> >> > Do we have to take other handlers than the OS handlers and the Cygwin
> >> > handlers into account?  Cygwin apps don't install SEH handlers, do
> >> > they?  Or do C++ apps?
> >> 
> >>   Nope, they don't, but that will probably not be the case forever, there are
> >> (long-term) moves afoot to get SEH support into the compiler.  However, we're
> >> in early startup-and-init here; we don't need to worry about what the
> >> application will do once it finally gets going.
> >
> >Sorry, but AFAICS we are not in early startup-and-init.  The threads.dll
> >library is a run-time loaded DLL via dlopen due to the
> >
> >  use threads;
> >
> >statement in the script.  This situation can occur at any point
> >during the runtime of an application.
> 
> 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

I didn't make a claim, I asked.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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