X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Wed, 15 Jul 2009 23:01:43 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please 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:	<20090716030143.GC13329@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<894CDBC00A124EF386FE3A334A73DFB8 AT multiplay DOT co DOT uk> <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>
MIME-Version:	1.0
In-Reply-To:	<6910a60907151907g69912353m46ee55d094603021@mail.gmail.com>
User-Agent:	Mutt/1.5.20 (2009-06-14)
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

On Thu, Jul 16, 2009 at 04:07:23AM +0200, Reini Urban wrote:
>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.

I can reproduce it.  It looks like perl (or more likely Windows) is adding
something extra to the SEH chain.  I'm too tired to track it down any further
tonight though.

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

- Raw text -