Date: Mon, 11 Mar 2013 16:45:54 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: deadlock with busy waiting on sigfe
Message-ID: <20130311204554.GA959@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <kd2d69$lam$1@ger.gmane.org> <20130116014646.GB13175@ednor.casa.cgf.cx> <20130116021414.GA14341@ednor.casa.cgf.cx> <kdfuvh$a93$1@ger.gmane.org> <20130120065456.GC17644@ednor.casa.cgf.cx> <khk62q$6n2$1@ger.gmane.org> <20130311143630.GA6498@ednor.casa.cgf.cx> <khlbm8$5tg$1@ger.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <khlbm8$5tg$1@ger.gmane.org>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.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