Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
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
X-Authenticated: #14308112
Date: Thu, 6 Oct 2005 16:18:39 +0300
From: Pavel Tsekov <ptsekov@gmx.net>
To: cygwin@cygwin.com
Subject: Re: handle_threadlist_exception: handle_threadlist_exception called  with threadlist_ix -1
In-Reply-To: <20050901144331.GH18595@trixie.casa.cgf.cx>
Message-ID: <Pine.CYG.4.58.0510061616570.1556@mordor>
References: <SERRANOzGZuNY1SWoBD0000004f@SERRANO.CAM.ARTIMI.COM>  <20050901144331.GH18595@trixie.casa.cgf.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Y-GMX-Trusted: 0
X-IsSubscribed: yes

On Thu, 1 Sep 2005, Christopher Faylor wrote:

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

I am can reproduce this repeatedly - I'll try to isolate the cause and
post a test case.

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

