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=SCqrz3pi4+7kdC0+N+1xGsySw5Dufh1smLBW0iXEOfHkIAmaWMtlM
	TQzzc48eiuPH2zmbGWIxdnej/lzVv4SVwtf8T0CLYrWZAUTzwVYsJ6gBpPZBD2ck
	RV6e4vB6JDXLnekaYWRE03J52uW5SStxDGjj62rZBguzemHHR5anDc=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Tue, 1 Dec 2015 12:20:37 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: fork issue when lauching cygwin64 process from 32bit native app on Windows 10 TH2
Message-ID: <20151201112037.GU2755@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <565D762E DOT 4090109 AT gmail DOT com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="opqKFQYYH8F8WaoB"
Content-Disposition: inline
In-Reply-To: <565D762E.4090109@gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)

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

On Dec  1 19:27, nu774 wrote:
> After upgrading to Windows 10 TH2 (ver 1511, build 10586), any attempt
> to launch a cygwin64 process from 32bit native app (for example,
> C:\windows\syswow64\cmd.exe) *always* results in a fork error.
>=20
> To be precise, I can execute 64bit bash.exe from 32bit cmd.exe.
> However, this bash process never succeeds in forking a child (ls or
> something).
> Also, I cannot launch 64bit mintty.exe from 32bit cmd.exe. It always
> fails in a error dialog saying that:
>=20
> mintty: could not detach from caller
> Try '--help' for more information.
>=20
> When launching from 64bit app, this issue doesn't happen.

I don't have a W10 ver 1511 yet, but even then it's hard to see that
this may be Cygwin's fault.  It worked so far with all versions of
Windows since XP 64, including the pre-1511 W10.

There must be a bug in the new CMD somewhere.  But, anyway, I'll look
into it when I finally managed to update my W10 test machine.


Corinna

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

--opqKFQYYH8F8WaoB
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWXYKFAAoJEPU2Bp2uRE+g/loP/jAFlk9cJE8GShPqPQQaSa2t
HitiC4NbzfmmlYHCvAu6az6RrN3EuKM47jZMqMJALCvbrcprEkXy/jQc+PF1oKec
SwBfago2pNmTkWX0ScPqRW7vA8P4NzAc+Gbq05JWe0mUYoqxusiSF1QHrDfmQJBx
3zdLpUnjGoP7S+fosv6xiwlXj0v66b4tmoZdFk7YX7y3BAirrwjPO8Ex3i1IBwVT
Tb1XdDttMzJvu+c0jQCRyM8w/4MOQvG1el4JRh2LRqYzc8ud0snERkue6UL+Lm5V
XTdPI3LKltnUH4UGxvrBTENKKL0RNtjYUYphWKgLmBgWOM2wTlI4UHZKGEjzwDOx
P82FEoPOokOjJA1znxKlYya7IpY1YgBMSpzVOkaFsovxQvoTjKKLNOFX1QR2ylRd
NbwqVRQy+B8tRy2kAMHFADzlcfseXnlchfnTy+5KLII5WqIFiVvi6xilrLyRGnUp
ywB8Xf3xoThqODgOnbiE9INWs71amkwnCBg93plwXcEVOy/ccyMtaWsLp6+LIG2u
nQ6Lb3PhPBgfVQYDb/KllHYweAO1iUaiGGwRt+LY0K+/JPmGbYLbf+f2f/s6/q4M
G3BKKRPjQtAFZxjf6mt3NpfqHHK6trmcVwpnVn5oCCFl5EYCS62hTLkNRuv75z/D
jg26TggkVCk9QhFTYe5/
=8WSd
-----END PGP SIGNATURE-----

--opqKFQYYH8F8WaoB--