From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32280 invoked by alias); 22 Dec 2012 02:49:56 -0000 Received: (qmail 32271 invoked by uid 22791); 22 Dec 2012 02:49:54 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,TW_CG 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; Sat, 22 Dec 2012 02:49:44 +0000 Received: from pool-173-76-51-117.bstnma.fios.verizon.net ([173.76.51.117] helo=cgf.cx) by mho-01-ewr.mailhop.org with esmtpa (Exim 4.72) (envelope-from ) id 1TmF9k-0003Aw-4C for cygwin@cygwin.com; Sat, 22 Dec 2012 02:49:44 +0000 Received: from localhost (ednor.casa.cgf.cx [192.168.187.5]) by cgf.cx (Postfix) with ESMTP id 3800913C076 for ; Fri, 21 Dec 2012 21:49:43 -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/cWHUGy/2w3cfsRISvuoQD Date: Sat, 22 Dec 2012 02:49:00 -0000 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Intermittent failures retrieving process exit codes - snapshot test requested Message-ID: <20121222024943.GA5773@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> <20121221161024.GA10871@ednor.casa.cgf.cx> <20121221170219.GF18188@calimero.vinschen.de> <20121221193620.GA29203@ednor.casa.cgf.cx> <50D4E144.706@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50D4E144.706@gmail.com> 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/msg00339.txt.bz2 On Fri, Dec 21, 2012 at 11:23:00PM +0100, marco atzeri wrote: >On 12/21/2012 8:36 PM, Christopher Faylor wrote: >> 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 >> > >I think the Xserver doesn't like it. >on 20121221 it freezes on start on W7/64 >no issue on 20121218 I acdtually tried Xserver before submitting my change so it certainly isn't a consistent 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