From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8238 invoked by alias); 11 Mar 2013 20:46:22 -0000 Received: (qmail 8213 invoked by uid 22791); 11 Mar 2013 20:46:16 -0000 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 Received: from mho-03-ewr.mailhop.org (HELO mho-01-ewr.mailhop.org) (204.13.248.66) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 11 Mar 2013 20:45:55 +0000 Received: from pool-108-20-146-82.bstnma.fios.verizon.net ([108.20.146.82] helo=cgf.cx) by mho-01-ewr.mailhop.org with esmtpa (Exim 4.72) (envelope-from ) id 1UF9bX-0000T0-9g for cygwin@cygwin.com; Mon, 11 Mar 2013 20:45:55 +0000 Received: from localhost (ednor.casa.cgf.cx [192.168.187.5]) by cgf.cx (Postfix) with ESMTP id 7950588041D for ; Mon, 11 Mar 2013 16:45:54 -0400 (EDT) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Report-Abuse-To: abuse@dyndns.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 20:46:00 -0000 From: Christopher Faylor 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: <20130116014646.GB13175@ednor.casa.cgf.cx> <20130116021414.GA14341@ednor.casa.cgf.cx> <20130120065456.GC17644@ednor.casa.cgf.cx> <20130311143630.GA6498@ednor.casa.cgf.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2013-03/txt/msg00212.txt.bz2 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