From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6330 invoked by alias); 2 Jan 2013 21:41:26 -0000 Received: (qmail 6271 invoked by uid 22791); 2 Jan 2013 21:41:24 -0000 X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,KHOP_SPAMHAUS_DROP,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mho-03-ewr.mailhop.org (HELO mho-01-ewr.mailhop.org) (204.13.248.66) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 02 Jan 2013 21:41:18 +0000 Received: from pool-98-110-183-21.bstnma.fios.verizon.net ([98.110.183.21] helo=cgf.cx) by mho-01-ewr.mailhop.org with esmtpa (Exim 4.72) (envelope-from ) id 1TqW3p-000KXm-Ir for cygwin@cygwin.com; Wed, 02 Jan 2013 21:41:17 +0000 Received: from localhost (ednor.casa.cgf.cx [192.168.187.5]) by cgf.cx (Postfix) with ESMTP id E53798805B5 for ; Wed, 2 Jan 2013 16:41:16 -0500 (EST) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX188pv5HkkTR/Lq6QZeJqq+2 Date: Wed, 02 Jan 2013 21:41:00 -0000 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Intermittent failures retrieving process exit codes - snapshot test requested Message-ID: <20130102214116.GA6540@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <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> <50E49E37.1060200@dancol.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50E49E37.1060200@dancol.org> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2013-01/txt/msg00033.txt.bz2 On Wed, Jan 02, 2013 at 12:53:11PM -0800, Daniel Colascione wrote: >On 1/2/13 12: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. > >What do you mean? ExitThread should never return, and I can't >imagine anything on the thread termination path calling ExitThread >again, especially not once the thread jumps to kernel mode. Sorry, I was just speculating about what it looked like. I'm still debugging the problem. 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