This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: perl threads on 2008 R2 64bit = crash ( was: perl 5.10 threads on 1.5.25 = instant crash )
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