This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: handle_threadlist_exception: handle_threadlist_exception called with threadlist_ix -1


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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]