X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-4.8 required=5.0	tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,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:132.245.1.149;KIP:(null);UIP:(null);IPV:NLI;H:BLUPRD0512HT003.namprd05.prod.outlook.com;RD:none;EFVD:NLI
X-SpamScore: -2
X-BigFish: PS-2(zzbb2dI98dI9371Ic1dMzz1ee6h1de0h1202h1e76h1d1ah1d2ahzzb412mz32i2a8h668h839h947hd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1765h18e1h1155h)
Message-ID: <50FF56F4.8090007@coverity.com>
Date: Tue, 22 Jan 2013 22:20:20 -0500
From: Tom Honermann <thonermann AT coverity DOT com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: <cygwin AT cygwin DOT com>
Subject: Re: Intermittent failures with ctrl-c
References: <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> <50F9AC57 DOT 5020309 AT coverity DOT com> <20130119055833 DOT GA23653 AT ednor DOT casa DOT cgf DOT cx> <50FC6AF2 DOT 7070501 AT coverity DOT com>
In-Reply-To: <50FC6AF2.7070501@coverity.com>
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/20/2013 05:08 PM, Tom Honermann wrote:
> However, I was still able to reproduce another case.  As before, one of
> the processes is being left running when the rest are terminated.  The
> "abandoned" process appears to be in a live-lock state with two threads
> (threads 1 and 2) running at 100%.  Of particular interest is that each
> time I press ctrl-c in the cmd.exe console this process was spawned
> from, a new thread appears in the process even though this program is no
> longer a foreground process and all other Cygwin processes have
> terminated.  The new threads never exit.

I noticed that more changes were checked in that looked like they might 
address this, so I tested again with the latest snapshot (20130123).

I wasn't able to reproduce any of the symptoms I previously reported.  Yay!

However, just as I was about to give up testing, I hit one more new 
issue.  One of the ctrl-c events sent bash into what appeared to be an 
infinite loop emitting error messages like these:

11408974 [unknown (0x144C)] bash 1752 exception::handle: Error while 
dumping state (probably corrupted stack)
11411584 [unknown (0x144C)] bash 1752 exception::handle: Error while 
dumping state (probably corrupted stack)

While this was going on, hitting ctrl-c had no discernible effect.  I 
resorted to killing the process via task manager.

This only occurred once, I wasn't able to get it to happen again.

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