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

["Steven Hartland" <killing at multiplay dot co dot uk>]

----- Original Message ----- 
From: "Christopher Faylor" <cgf-use-the-mailinglist-please@cygwin.com>
To: <cygwin@cygwin.com>
Sent: Wednesday, July 15, 2009 1:03 AM
Subject: Re: perl threads on 2008 R2 64bit = crash ( was: perl 5.10 threads on 1.5.25 = instant crash )


> On Wed, Jul 15, 2009 at 12:36:56AM +0100, Steven Hartland wrote:
> > 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.
>
> No, sorry, it really doesn't help.  The VC++ debugger doesn't know how
> to handle cygwin exceptions.

Was just trying to get a hint of the area of the problem since gdb doesn't
actually break when it happens this seemed to be the only way to get that
info.

Any pointers on how I can help narrow down the issue?

   Regards
   Steve


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