perl threads on 2008 R2 64bit = crash ( was: perl 5.10 threads on 1.5.25 = instant crash )

Thu Jul 16 16:39:00 GMT 2009

On Jul 15 23:01, Christopher Faylor wrote:
> 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.

http://cygwin.com/ml/cygwin/2009-07/msg00584.html
Do you have an idea?
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