X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By:	sourceware.org
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX1/xqKwlIAbD++hXzDkH+o6D
Date:	Mon, 11 Mar 2013 16:45:54 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: deadlock with busy waiting on sigfe
Message-ID:	<20130311204554.GA959@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<kd2d69$lam$1 AT ger DOT gmane DOT org> <20130116014646 DOT GB13175 AT ednor DOT casa DOT cgf DOT cx> <20130116021414 DOT GA14341 AT ednor DOT casa DOT cgf DOT cx> <kdfuvh$a93$1 AT ger DOT gmane DOT org> <20130120065456 DOT GC17644 AT ednor DOT casa DOT cgf DOT cx> <khk62q$6n2$1 AT ger DOT gmane DOT org> <20130311143630 DOT GA6498 AT ednor DOT casa DOT cgf DOT cx> <khlbm8$5tg$1 AT ger DOT gmane DOT org>
MIME-Version:	1.0
In-Reply-To:	<khlbm8$5tg$1@ger.gmane.org>
User-Agent:	Mutt/1.5.20 (2009-06-14)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

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?

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -