X-Recipient: archive-cygwin AT delorie DOT com 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 X-Mail-Handler: Dyn Standard SMTP by Dyn X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX19yxB3sNZ95gJKfUOTb42S3 Date: Fri, 21 Dec 2012 14:36:20 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Intermittent failures retrieving process exit codes - snapshot test requested Message-ID: <20121221193620.GA29203@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <50C2498C DOT 2000003 AT coverity DOT com> <50C276AC DOT 9090301 AT mailme DOT ath DOT cx> <50D401EF DOT 9040705 AT coverity DOT com> <20121221103241 DOT GD18188 AT calimero DOT vinschen DOT de> <20121221161024 DOT GA10871 AT ednor DOT casa DOT cgf DOT cx> <20121221170219 DOT GF18188 AT calimero DOT vinschen DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20121221170219.GF18188@calimero.vinschen.de> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Fri, Dec 21, 2012 at 06:02:19PM +0100, Corinna Vinschen wrote: >On Dec 21 11:10, Christopher Faylor wrote: >> 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. > >Right. I guess the question is how to synchronize things so that the >thread calling TerminateProcess is actually the last one, making sure >its return value is used. > >Maybe the NtQueryInformationThread(ThreadAmILastThread) call is of some >help. Or we have to keep all thread IDs of the self-started threads >available to terminate them explicitely at process exit. I checked in a complicated fix for this problem which only affected Cygwin-created threads. But, then, I thought about another riskier but simpler fix. That version is now in CVS and I'm generating a new snapshot with it. I tested this lightly on Windows 7 and 32-bit XP but it would be nice to hear if multi-threaded things like X work on other platforms too. If you test a snapshot, note that I'm still tracking down Ken Brown's reporte emacs regression in recent snapshots so that will still be broken. 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