X-Spam-Check-By:	sourceware.org
Date:	Thu, 13 Jul 2006 12:32:15 -0400
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: 1.5.20: Occasional crash at address 0x6100365f (cygthread::stub() in cygthread.cc)
Message-ID:	<20060713163215.GA6003@trixie.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<e8stdb$f1d$1 AT sea DOT gmane DOT org>
Mime-Version:	1.0
In-Reply-To:	<e8stdb$f1d$1@sea.gmane.org>
User-Agent:	Mutt/1.5.11
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On Mon, Jul 10, 2006 at 04:51:21PM +1000, Kiyo Kelvin Lee wrote:
>Using 1.5.20, occasionally sh.exe would crash with the standard Windows 
>crash dialog with these information:
>
>[sh.exe - Application Error]
>The instruction at "0x6100365f" referenced memory at "0x006cda90". The 
>memory could not be "written".
>Click on OK to terminate the program.
>Click on CANCEL to debug the program.
>
>Tested snapshot 20060707 and the problem persists.
>
>With gdb, I found the address corresponding to the function 
>cygthread:stub() of cygthread.cc (snapshot 20060707) at line 65:
>	_my_tls._ctinfo = info;
>
>Reported the problem before but, however, I hope the little further 
>information can help resolving the problem.

Is /bin/sh.exe bash or ash on your system.

Also, could you include the cygcheck output as mentioned at
http://cygwin.com/problems.html ?

I appreciate that you've taken the steps to debug this but without a way
to duplicate the problem there isn't much that can be done.  I've run
both bash and ash in every way I could think of to duplicate this
problem with no success.  I'm stumped as to how and why a cygthread
could be firing while a process is exiting.

If you can capture this state in gdb and get backtraces of all of the
running threads, that would probably help.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -