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
Date: Tue, 11 Oct 2005 11:01:27 -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: <20051011150127.GB14140@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> <20051006150019 DOT GA6197 AT trixie DOT casa DOT cgf DOT cx> <Pine DOT CYG DOT 4 DOT 58 DOT 0510061840550 DOT 1524 AT mordor> <Pine DOT CYG DOT 4 DOT 58 DOT 0510111733550 DOT 1460 AT mordor>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.CYG.4.58.0510111733550.1460@mordor>
User-Agent: Mutt/1.5.8i

On Tue, Oct 11, 2005 at 05:51:00PM +0300, Pavel Tsekov wrote:
>On Thu, 6 Oct 2005, Pavel Tsekov wrote:
>
>> On Thu, 6 Oct 2005, Christopher Faylor wrote:
>>
>> > >It might be a different problem but the message is the same.
>> >
>> > It *is* a different problem.
>>
>> Ok.
>>
>> > Some thread is sending a signal 31 (SIGUSR1).  Which thread is doing this?
>>
>> An application thread signaling another thread to stop its execution. I am
>> on it - I'll report back if I manage to find something.
>
>While tracking this problem I found what I suspect is a small bug in
>the way sigsuspend() works when it is used to retrieve the list of pending
>signals for a thread other than the main one. I think this is related to
>the crash I am seeing in some way though this has to be determined yet.

See the FIXME a few lines down from that.

>As I read the code, when retrieving the list of pending signals
>sigpending() inspects only the list of blocked signals for the main
>thread - it doesn't look in the thread specific list of blocked signals
>of the calling thread.

So, it sounds like you're pretty close to a PTC.

I don't see how ignoring blocked signals would cause a SEGV however.

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/