From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31043 invoked by alias); 6 Dec 2015 14:11:51 -0000 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 Received: (qmail 31030 invoked by uid 89); 6 Dec 2015 14:11:51 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_PBL,RDNS_DYNAMIC autolearn=no version=3.3.2 X-HELO: calimero.vinschen.de Received: from ipbcc02fe8.dynamic.kabel-deutschland.de (HELO calimero.vinschen.de) (188.192.47.232) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 06 Dec 2015 14:11:50 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 6FDDAA80629; Sun, 6 Dec 2015 15:11:48 +0100 (CET) Date: Sun, 06 Dec 2015 14:11:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: fork issue when lauching cygwin64 process from 32bit native app on Windows 10 TH2 Message-ID: <20151206141148.GD17433@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <565D762E.4090109@gmail.com> <20151201112037.GU2755@calimero.vinschen.de> <565D8D88.4080601@gmail.com> <20151201140105.GW2755@calimero.vinschen.de> <565DDB8E.1090609@gmail.com> <565DF5E8.5010908@blaeu.com> <5661C0AC.8050209@tlinx.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="9dgjiU4MmWPVapMU" Content-Disposition: inline In-Reply-To: <5661C0AC.8050209@tlinx.org> User-Agent: Mutt/1.5.23 (2014-03-12) X-SW-Source: 2015-12/txt/msg00065.txt.bz2 --9dgjiU4MmWPVapMU Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 1068 On Dec 4 08:34, Linda Walsh wrote: > Rob van Eijk wrote: > > > >Op 1-12-2015 om 17:40 schreef David Macek: > >>On 1. 12. 2015 15:01, Corinna Vinschen wrote: > >>>If that only happens w/ 64 bit Cygwin started from a 32 bit parent, th= en > >>>there's some foul-up in the WOW64 layer in terms of starting 64 bit > >>>processes, perhaps. Sigh, it's a rather unexpected change after it > >>>worked fine for so long :( > >>Yup. I can confirm. > ---- > Win10 has a 32-bit version? >=20 > I thought MS said Win8 was the last version that would > ship in a 32-bit version with their eventual intension to be getting > rid of 32-bit support entirely (for reasons like it supporting > various legacy design constraints that make it harder to manage(control) > as an end-user-platform, for example)? I guess given that the ARM version is 32 bit anyway, it didn't hurt to keep the 32 bit i686 version running as well. Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --9dgjiU4MmWPVapMU Content-Type: application/pgp-signature Content-length: 819 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWZEIkAAoJEPU2Bp2uRE+gDc4P/1IVUnAOaw51zA9oZAXhyqqn dkA2a6CL/zwlJ6Erg9NpMpVq7VP7hGIvZw6Py6iFAxi96IyRCpQA0hilOGbvr6I2 +p/iP+HcvwO/ZEtn5T1T0ZWSDOrLd5JzgWklAlSFlAUV8bioaCnIHmOxEZlK5H8p LFHF3OBhQHMQw9fLX32OHhgscOVT169i6S5aqnN2Di/9bg9ixEjLoEvK7NJmQc40 laBRqFKQSCRzyFm1kob8pjxYVCFL3kPO1hLAAHBQVtfQ4zB1nrTQp2t/Dtk5aX8y QmwREPqfTaZxn2o9k4z3VRUJJolbg8KxJQxeKc5JO2ip+Lv1lLW5IzvnWDqszsN/ chg8eyOwqQ8XjBdfEv/P2yu7oxm5QVbMJFeVvC3sxo1U0qv3FsBWIROMD0x/sgty SfjZNqjMBhqBn5Lv9BtK6WYUqxxUPG4v+puf2Ky/yyldIIDLzGbOxRGc+9ijDH3P rsiuG0PiuTI+ptjwKkERjg2rAe+I51g/wSLlLKXnSDn4Cj2CL23bFFgEYCH5B5xz DStaYlbIiQzH571YTB7UZkcNz4Qjli+wKdsnU+DL7RviZ2/TANHYWagqKpZ8jah5 mtx2A3tRk8qwvMIVuxXTZgKJIubDMAOa/nXRvhyhY48ytCLIeJCNCg15fyqNNiA2 Hz9I7d9RGBhbuWTA+m1B =ClPR -----END PGP SIGNATURE----- --9dgjiU4MmWPVapMU--