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:BY2PRD0512HT004.namprd05.prod.outlook.com;RD:none;EFVD:NLI
X-SpamScore: -8
X-BigFish: PS-8(zzbb2dI98dI9371I146dM1432Izz1ee6h1de0h1202h1e76h1d1ah1d2ahzz177df4h17326ah75dfh8275bhz32i2a8h668h839h947hd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1765h1155h)
Message-ID: <50F70C6F.4030903@coverity.com>
Date: Wed, 16 Jan 2013 15:24:15 -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: <50DCB454 DOT 9030400 AT coverity DOT com> <20121229215725 DOT GA18847 AT ednor DOT casa DOT cgf DOT cx> <50E23F98 DOT 1060004 AT coverity DOT com> <20130101053606 DOT GB18911 AT ednor DOT casa DOT cgf DOT cx> <50E48743 DOT 5040401 AT coverity DOT com> <20130102204821 DOT GA6524 AT ednor DOT casa DOT cgf DOT cx> <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> <20130116191433 DOT GA20563 AT ednor DOT casa DOT cgf DOT cx>
In-Reply-To: <20130116191433.GA20563@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 02:14 PM, Christopher Faylor wrote:
> Again, if I hit CTRL-C while running ./test.bat in mintty then test.bat
> exits immediately, as expected.  Hitting ctrl-c repeatedly after that
> point gives me a new bash prompt.

Yes, that is what is expected to happen.  What I am reporting is that 
interrupting test.bat sometimes leaves hung processes still running 
after control is returned to the shell.

> Non-exiting behavior was a symptom of a previous snapshot which was
> mentioned here:
>
> http://cygwin.com/ml/cygwin/2013-01/msg00164.html

I'm testing a newer snapshot than that one.  I'm been testing with 
20130114 which Thomas reported as no longer having that problem here:

http://cygwin.com/ml/cygwin/2013-01/msg00196.html

>> I rather doubt that the use of a .bat file is necessary to reproduce
>> this hang, but I haven't tried producing a test case that doesn't use a
>> .bat file.  This is a test case I was using when debugging the
>> intermittent incorrect exit code issue.
>
> Btw, an incorrect exit code is still a possibility if you're running
> from a cmd shell since it is possible to interrupt a cygwin process
> before cygwin is entirely set up.  That will cause a normal windows
> CTRL-C exit.

Yup, that is understood and expected.

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