Message-ID: <50E4A597.1060600@coverity.com>
Date: Wed, 2 Jan 2013 16:24:39 -0500
From: Tom Honermann <thonermann@coverity.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@cygwin.com>
Subject: Re: Intermittent failures retrieving process exit codes - snapshot test requested
References: <20121222024943.GA5773@ednor.casa.cgf.cx> <20121222031430.GA8355@ednor.casa.cgf.cx> <50D57818.1070706@gmail.com> <20121222175041.GA14475@ednor.casa.cgf.cx> <20121223165621.GA9935@ednor.casa.cgf.cx> <50DCB454.9030400@coverity.com> <20121229215725.GA18847@ednor.casa.cgf.cx> <50E23F98.1060004@coverity.com> <20130101053606.GB18911@ednor.casa.cgf.cx> <50E48743.5040401@coverity.com> <20130102204821.GA6524@ednor.casa.cgf.cx>
In-Reply-To: <20130102204821.GA6524@ednor.casa.cgf.cx>
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/02/2013 03:48 PM, Christopher Faylor wrote:
> I managed to duplicate a hang by really stressing ctrl-c a loop.  It
> uncovers some rather amazing Windows behavior which I have to think
> about.  Apparently ExitThread can be called recursively within the
> thread that Windows creates to handle CTRL-C.

I'm glad you could reproduce.  Based on your description, this sounds 
like a separate issue and not a regression introduced by the workarounds 
you put in place for the ExitProcess / ExitThread race.  Correct?

I wonder if this is the same issue I'm experiencing though.  I'm only 
pressing ctrl-c once and it sounds like you might be deliving a ctrl-c 
to the same process multiple times.  That may not be relevant to the 
root cause however.

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