From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13642 invoked by alias); 21 Dec 2012 16:10:37 -0000 Received: (qmail 13364 invoked by uid 22791); 21 Dec 2012 16:10:33 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mho-04-ewr.mailhop.org (HELO mho-02-ewr.mailhop.org) (204.13.248.74) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 21 Dec 2012 16:10:25 +0000 Received: from pool-173-76-51-117.bstnma.fios.verizon.net ([173.76.51.117] helo=cgf.cx) by mho-02-ewr.mailhop.org with esmtpa (Exim 4.72) (envelope-from ) id 1Tm5B3-000EP6-AR for cygwin@cygwin.com; Fri, 21 Dec 2012 16:10:25 +0000 Received: from localhost (ednor.casa.cgf.cx [192.168.187.5]) by cgf.cx (Postfix) with ESMTP id 4567E13C076 for ; Fri, 21 Dec 2012 11:10:24 -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: U2FsdGVkX1+P987QCgiYddlVzgNVFEx3 Date: Fri, 21 Dec 2012 16:10:00 -0000 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Intermittent failures retrieving process exit codes Message-ID: <20121221161024.GA10871@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <50C2498C.2000003@coverity.com> <50C276AC.9090301@mailme.ath.cx> <50D401EF.9040705@coverity.com> <20121221103241.GD18188@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20121221103241.GD18188@calimero.vinschen.de> 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: 2012-12/txt/msg00315.txt.bz2 On Fri, Dec 21, 2012 at 11:32:41AM +0100, Corinna Vinschen wrote: >Maybe the signal thread should really not exit by itself, but just >wait until the TerminateThread is called. Chris? If the analysis is correct, that just fixes one symptom doesn't it? There are potentially many threads running in any Cygwin program and it sounds like any one of them could trigger this. 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