delorie.com/archives/browse.cgi | search |
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 |
From: | "Dave Korn" <dave DOT korn AT artimi DOT com> |
To: | <cygwin AT cygwin DOT com> |
Subject: | handle_threadlist_exception: handle_threadlist_exception called with threadlist_ix -1 |
Date: | Thu, 1 Sep 2005 15:25:17 +0100 |
MIME-Version: | 1.0 |
Message-ID: | <SERRANOzGZuNY1SWoBD0000004f@SERRANO.CAM.ARTIMI.COM> |
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? cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |