X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-4.4 required=5.0	tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By: sourceware.org
X-Forefront-Antispam-Report: CIP:157.56.238.5;KIP:(null);UIP:(null);IPV:NLI;H:BY2PRD0512HT003.namprd05.prod.outlook.com;RD:none;EFVD:NLI
X-SpamScore: -2
X-BigFish: PS-2(zzbb2dI98dI9371Izz1ee6h1de0h1202h1e76h1d1ah1d2ahzzz32i2a8h668h839h947hd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1765h1155h)
Message-ID: <50F9AC57.5020309@coverity.com>
Date: Fri, 18 Jan 2013 15:11:03 -0500
From: Tom Honermann <thonermann AT coverity DOT com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: <cygwin AT cygwin DOT com>
Subject: Re: Intermittent failures with ctrl-c
References: <50E4A597 DOT 1060600 AT coverity DOT com> <50F5D559 DOT 4090909 AT coverity DOT com> <20130116020420 DOT GA13284 AT ednor DOT casa DOT cgf DOT cx> <50F6D757 DOT 3000005 AT coverity DOT com> <50F6DB0F DOT 2020602 AT gmail DOT com> <50F6E695 DOT 20302 AT coverity DOT com> <CA+sc5mng_tHVwtzrPBexggCRzTWanNWEHBY0mfP43KhXZgrA=A AT mail DOT gmail DOT com> <50F6F69F DOT 3040000 AT coverity DOT com> <20130116185908 DOT GA17801 AT ednor DOT casa DOT cgf DOT cx> <50F70B27 DOT 8000904 AT coverity DOT com> <20130116222305 DOT GA24529 AT ednor DOT casa DOT cgf DOT cx>
In-Reply-To: <20130116222305.GA24529@ednor.casa.cgf.cx>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginatorOrg: coverity.com
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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 01/16/2013 05:23 PM, Christopher Faylor wrote:
> On Wed, Jan 16, 2013 at 03:18:47PM -0500, Tom Honermann wrote:
> I managed to duplicate a hang by changing your .bat file to use "sleep
> 2" rather than false.  I'm investigating now.

I noticed that you checked in some additional changes on the 16th that 
look related to this, so I tested again with today's snapshot (20130118).

I was still able to produce hangs using the same test case.  The 
symptoms are slightly different than I had seen previously.  bash hung 2 
out of the ~60 times I interrupted the test.  No error messages were 
displayed this time.  Upon pressing ctrl-c, bash hung for 60 seconds.  I 
was then greeted with the "Terminate batch job" prompt and responding 
'Y' terminated the process tree as expected.  Pressing ctrl-c while bash 
was hung for that 60 seconds appeared to have no affect.

My apologies for this distraction if you don't yet expect this to be fixed.

Tom.


--
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