X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 	tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS,WEIRD_PORT
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <6910a60907151907g69912353m46ee55d094603021@mail.gmail.com>
References: <DAFA8ADC28014B82920B6D6AB81A1633@multiplay.co.uk> 	 <20090714185506.GB12236@ednor.casa.cgf.cx> 	 <20090714190436.GO27613@calimero.vinschen.de> 	 <C795A3B019414FFC84425368B30B83F1@multiplay.co.uk> 	 <20090714200631.GP27613@calimero.vinschen.de> 	 <F24D5DF71BEC447DB0E080A0D6451ABB@multiplay.co.uk> 	 <20090714205617.GA12534@ednor.casa.cgf.cx> 	 <8541BCA91FF64580AA7A8065FBF9C938@multiplay.co.uk> 	 <39B3B148DA514671BB2E1AE46946169C@multiplay.co.uk> 	 <6910a60907151907g69912353m46ee55d094603021@mail.gmail.com>
Date: Thu, 16 Jul 2009 04:21:41 +0200
Message-ID: <6910a60907151921l1018abffof196d7bd230d9287@mail.gmail.com>
Subject: Re: perl threads on 2008 R2 64bit = crash ( was: perl 5.10 threads on  	1.5.25 = instant crash )
From: Reini Urban <rurban@x-ray.at>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
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

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

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

