Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Date:	Thu, 1 Sep 2005 10:43:31 -0400
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: handle_threadlist_exception: handle_threadlist_exception called with threadlist_ix -1
Message-ID:	<20050901144331.GH18595@trixie.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
References:	<SERRANOzGZuNY1SWoBD0000004f AT SERRANO DOT CAM DOT ARTIMI DOT COM>
Mime-Version:	1.0
In-Reply-To:	<SERRANOzGZuNY1SWoBD0000004f@SERRANO.CAM.ARTIMI.COM>
User-Agent:	Mutt/1.5.8i

On Thu, Sep 01, 2005 at 03:25:17PM +0100, Dave Korn wrote:
>
>  Anyone else seeing quite a lot of these with current cvs HEAD?  Often when
>pressing Ctrl-C, sometimes when things exit for other (signal-related?)
>reasons?
>
>  I think this error indicates that a signal has been received but either
>find_tls hasn't yet been called, or something has overwritten the threadlist
>index.  There's a lot that goes on at startup/fork time, though, and I'm not
>deeply familiar with it.  Since I'm set up for debugging ATM, does anyone
>have any suggestions where I could look next?

How about looking in the direction of a simple test scenario which demonstrates
what you are reporting?

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 -