DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=G35/72syHTC8VII5i3geTbfe3we24RXu3pSw9Hc6DDOR8UWVuz7W1
	s5UdwXzO3nYEsortnpQoFvaTbSzyVQX1b1bxoqiuQyNaiyVjBKTh3d64df9jP6/w
	BLJd9nVzVzaCBCm507VViWC00f9wh1hoON5nkmZZW2R/zy1lLh+zjw=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Thu, 14 Nov 2013 10:19:50 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Intermittent failures retrieving process exit codes
Message-ID: <20131114091950.GC526@calimero.vinschen.de>
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> <52844B2E.5050902@coverity.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="pZs/OQEoSSbxGlYw"
Content-Disposition: inline
In-Reply-To: <52844B2E.5050902@coverity.com>
User-Agent: Mutt/1.5.21 (2010-09-15)

--pZs/OQEoSSbxGlYw
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Tom,

On Nov 13 23:01, Tom Honermann wrote:
> On 12/21/2012 01:30 AM, Tom Honermann wrote:
> >[...]
> >When the race condition results in the undesirable outcome, the exit
> >code for the process is set to the exit code for the secondary thread's
> >call to ExitThread().  I can only speculate at this point, but my guess
> >is that the TerminateProcess() code disassociates the calling thread
> >from the process before other threads are stopped such that
> >ExitThread(), concurrently running in another thread, may determine that
> >the calling thread is the last thread of the process and overwrite the
> >process exit code.
> >[...]
>=20
> Time passes...
>=20
> I worked with some former colleagues to report this issue to
> Microsoft.  Windows 8.1 and Windows Server 2012 R2 contain a fix
> that addresses the test case above.  A hotfix has been made
> available for Windows 7 SP1 and Windows Server 2008 R2.  Should
> anyone desire a hotfix for other versions of Windows, it will be
> necessary to open a case with Microsoft to request it.
>=20
> http://support.microsoft.com/kb/2875501
>=20
> Tom.

thanks for letting us know!

I'm very glad to read that this is an OS bug and a fix is available.

At least partially.  I'm a bit confused.  As far as I understand it this
is the situation now:

  Vista/2008 and earlier:  no fix available.
  W7/2008R2:               only hotfix for manual installation
  W8/2012:                 no fix available.
  W8.1/2012R2:             fixed.

Did I get that right?  That sounds a bit weird...


Thanks again,
Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--pZs/OQEoSSbxGlYw
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)

iQIcBAEBAgAGBQJShJW2AAoJEPU2Bp2uRE+gFoQP/2KM0ZM1vVGzP7qanb9P2K1Z
OGzjQSPaSyX+e0g+VFkMByqgmcqN2S2fC4EZM41h6PFhGqIe4KGBlrtstnY6/AGc
fhu4p94sDnLs86Cnyn9p1VUwZMwqyi4JKXcz9tSUezi1RUczioP1jBZHOZjWBJdv
DkAPvGsFtFb2DujoXMSmujUnGwgQxwr1a9InpJzu9dcAKdW/pBuFeoQgOXSOqW0I
bSkUelCoOR3QNKnjoxwHzxgg0zLERi+IDKkIj0BHaFv9s2Gj9iVFue6VHIIQMDKp
XiOrAUZ16pcyswG6qDYwhZew/XwPyTWzSvpXyj153zOXPLgIXAzvM0FQK9v5XVYJ
57rDhgFTKvak21I13yNOiw5nyAfP4/K3DiqCKJIU/1huBDDSxgFbPe1/xTLqW22G
5UsXejisLhB6+oKwLzHPgn6eLWzpoCRtdTFxfAD/L+stYjF1sjDXKMlKuPauRVzJ
o+qeIOGGp1O52GESzXATcO485d+RRdA70Q6LgFpHVZpiakL8wjujCZ8eUEdGqXz9
d0m2wiEewIZU45K74jwkdYyBPleXMU+z2+B2+B8R9aoXnUvxN0atC50FwTx3hK2j
SC4FxCJkbNskdu+qsuoF6CFmoGQNqGq9Fpw3MIERkkRAIRdKejKYt7r/A0W+G0Me
HwgnNylR3fAJ2UiYAbrB
=ZD3g
-----END PGP SIGNATURE-----

--pZs/OQEoSSbxGlYw--