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 Date: Thu, 6 Oct 2005 10:19:33 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: handle_threadlist_exception: handle_threadlist_exception called with threadlist_ix -1 Message-ID: <20051006141933.GB17445@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <20050901144331 DOT GH18595 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i On Thu, Oct 06, 2005 at 04:18:39PM +0300, Pavel Tsekov wrote: >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. Did you happen to notice when the age of the message to which you're responding? Dave figured out the problem subsequent to sending the above. It was due to some object files not getting rebuilt after a change to cygtls.h. -- 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/