Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authenticated: #14308112 Date: Thu, 6 Oct 2005 16:18:39 +0300 From: Pavel Tsekov To: cygwin AT cygwin DOT 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: References: <20050901144331 DOT GH18595 AT trixie DOT casa DOT cgf DOT 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/