Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Thu, 6 Oct 2005 11:00:19 -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: <20051006150019.GA6197@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <SERRANOzGZuNY1SWoBD0000004f AT SERRANO DOT CAM DOT ARTIMI DOT COM> <20050901144331 DOT GH18595 AT trixie DOT casa DOT cgf DOT cx> <Pine DOT CYG DOT 4 DOT 58 DOT 0510061616570 DOT 1556 AT mordor> <20051006141933 DOT GB17445 AT trixie DOT casa DOT cgf DOT cx> <Pine DOT CYG DOT 4 DOT 58 DOT 0510061735120 DOT 1140 AT mordor>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.CYG.4.58.0510061735120.1140@mordor>
User-Agent: Mutt/1.5.8i

On Thu, Oct 06, 2005 at 05:39:35PM +0300, Pavel Tsekov wrote:
>On Thu, 6 Oct 2005, Christopher Faylor wrote:
>
>> 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.
>
>Yes. When I saw the error message I remembered that I've seen it on
>the mailing list already. So, I used the search engine to find on
>which date the message was posted and replied ot that post.
>
>It might be a different problem but the message is the same.

It *is* a different problem.

>And this is with a clean build of the dll from yesterday and a clean
>build of the software from today.  Here is a backtrace (just for the
>record):
>
>(gdb) bt
>#0  sigismember (set=0x162f090, sig=31) at
>../../../../src/winsup/cygwin/signal.cc:429
>#1  0x61017710 in sigpacket::process (this=0x6113b3ec) at
>../../../../src/winsup/cygwin/exceptions.cc:1072
>#2  0x61092b18 in wait_sig () at
>../../../../src/winsup/cygwin/sigproc.cc:1128
>#3  0x610033ef in cygthread::stub (arg=0xa2eff0) at
>../../../../src/winsup/cygwin/cygthread.cc:73
>#4  0x00000f94 in ?? ()
>#5  0x00000000 in ?? () from
>
>In frame 0 'set' is pointing at invalid memory - I am trying to determine
>why.

Some thread is sending a signal 31 (SIGUSR1).  Which thread is doing this?

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/