Message-ID: <50FF56F4.8090007@coverity.com>
Date: Tue, 22 Jan 2013 22:20:20 -0500
From: Tom Honermann <thonermann@coverity.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@cygwin.com>
Subject: Re: Intermittent failures with ctrl-c
References: <20130116020420.GA13284@ednor.casa.cgf.cx> <50F6D757.3000005@coverity.com> <50F6DB0F.2020602@gmail.com> <50F6E695.20302@coverity.com> <CA+sc5mng_tHVwtzrPBexggCRzTWanNWEHBY0mfP43KhXZgrA=A@mail.gmail.com> <50F6F69F.3040000@coverity.com> <20130116185908.GA17801@ednor.casa.cgf.cx> <50F70B27.8000904@coverity.com> <20130116222305.GA24529@ednor.casa.cgf.cx> <50F9AC57.5020309@coverity.com> <20130119055833.GA23653@ednor.casa.cgf.cx> <50FC6AF2.7070501@coverity.com>
In-Reply-To: <50FC6AF2.7070501@coverity.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.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