Date: Wed, 23 Jan 2013 00:26:50 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Intermittent failures with ctrl-c
Message-ID: <20130123052650.GA8723@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <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> <50FF56F4 DOT 8090007 AT coverity DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <50FF56F4.8090007@coverity.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Tue, Jan 22, 2013 at 10:20:20PM -0500, Tom Honermann wrote:
>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.

Was there a stackdump?

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