deadlock with busy waiting on sigfe

Christopher Faylor
Mon Mar 11 20:46:00 GMT 2013

On Tue, Mar 12, 2013 at 04:35:41AM +0900, jojelino wrote:
>On 2013-03-11 PM 11:36, Christopher Faylor wrote:
>> A "proper bug report" would at least include what you were actually doing
>> to trigger this problem.
>I was trying to CTRL+C cygwin python process that is executing some 
>operation and fell asleep for 60 seconds repeatedly. I'm pretty sure 
>that the process was sleeping as i tried interrupt it.
>> Are you sure that there are only two threads executing here?  It seems like
>> this is a symptom of another thread holding the lock.
>It's unlikely the case because there was two thread running when 
>livelock observed.

How about if you humor me and do a "show threads" rather than just
asserting that it was unlikely?


Problem reports:
Unsubscribe info:

More information about the Cygwin mailing list