X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Thu, 16 Jul 2009 11:03:26 +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: <20090716090326.GA17746@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20090714185506 DOT GB12236 AT ednor DOT casa DOT cgf DOT cx> <20090714190436 DOT GO27613 AT calimero DOT vinschen DOT de> <C795A3B019414FFC84425368B30B83F1 AT multiplay DOT co DOT uk> <20090714200631 DOT GP27613 AT calimero DOT vinschen DOT de> <F24D5DF71BEC447DB0E080A0D6451ABB AT multiplay DOT co DOT uk> <20090714205617 DOT GA12534 AT ednor DOT casa DOT cgf DOT cx> <8541BCA91FF64580AA7A8065FBF9C938 AT multiplay DOT co DOT uk> <39B3B148DA514671BB2E1AE46946169C AT multiplay DOT co DOT uk> <6910a60907151907g69912353m46ee55d094603021 AT mail DOT gmail DOT com> <6910a60907151921l1018abffof196d7bd230d9287 AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6910a60907151921l1018abffof196d7bd230d9287@mail.gmail.com>
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 16 04:21, Reini Urban wrote:
> 2009/7/16 Reini Urban:
> > 2009/7/15 Steven Hartland:
> >> This may or may not help:
> >>
> >> According to VC++ debugger it always dies with:
> >> Unhandled exception at 0x610d089d in perl.exe: 0xC0000005: Access violation
> >> reading location 0x00000004.
> >>
> >> According to gdb 0x610d089d = thread.cc:113
> >
> > Thanks!
> >
> > This looks like almost certainly a simple perl bug. Threads was Jerry Heddens
> > working arena lately, but there are complicated things going in core.
> > If it's easily reproducible best would be to start with a debugging perl
> > and break at the point which tries to read from 0x4.
> 
> Sorry, cannot reproduce either
> with the following perls: 5.8.5 5.8.5d 5.8.6 5.8.8 5.10.0 5.10.0d 5.11.0d
> under cygwin-1.5.25 and XP SP2
> and neither under latest cygwin-1.7.0

It's a Windows Server 2008 thingy.  MSFT added some code to the OS which
checks for the validity of the SEH chain.  The code is not compiled in
to the client OSes, only to the Server OSes.  We checked in a patch back
in early 2008 to deal with this mechanism.  That's probably the reason
that the C testcase works fine.  Apparently Perl adds something which
makes the SEH chain invalid again from 2008's point of view.

Btw., *everybody* can test on Windows Server 2008:
http://www.microsoft.com/downloads/details.aspx?familyid=B6E99D4C-A40E-4FD2-A0F7-32212B520F50


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