X-Recipient: archive-cygwin@delorie.com
X-Spam-Check-By: sourceware.org
Date: Thu, 16 Jul 2009 18:13:30 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: perl threads on 2008 R2 64bit = crash ( was: perl 5.10 threads 	on   1.5.25 = instant crash )
Message-ID: <20090716161330.GQ27613@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <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> <20090716030143.GC13329@ednor.casa.cgf.cx>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20090716030143.GC13329@ednor.casa.cgf.cx>
User-Agent: Mutt/1.5.19 (2009-02-20)
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

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

