From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 116522 invoked by alias); 2 Dec 2015 22:15:25 -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 116505 invoked by uid 89); 2 Dec 2015 22:15:24 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=3.4 required=5.0 tests=BAYES_00,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; Wed, 02 Dec 2015 22:15:23 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 1691AA8035D; Wed, 2 Dec 2015 23:15:21 +0100 (CET) Date: Wed, 02 Dec 2015 22:15: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: <20151202221521.GH18447@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> <565E14BA.60204@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="l76fUT7nc3MelDdI" Content-Disposition: inline In-Reply-To: <565E14BA.60204@gmail.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-SW-Source: 2015-12/txt/msg00026.txt.bz2 --l76fUT7nc3MelDdI Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 1486 On Dec 1 22:44, David Macek wrote: > On 1. 12. 2015 18:40, David Macek wrote: > > On 1. 12. 2015 15:01, Corinna Vinschen wrote: > >> On Dec 1 21:07, nu774 wrote: > >>>> 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. > >>> > >>> No, cmd.exe is just an example. Any 32bit process can be an trigger. > >>> I guess something has changed in TH2 kernel regarding process memory > >>> management or something that interferes cygwin's fork(). > >> > >> 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 :( > >=20 > > Yup. I can confirm. >=20 > Just for the record, we did some debugging over IRC and it seems it's an = issue with WOW64 where the stack in the first 64-bit process is offset for = some reason. >=20 > Citing Corinna: "I wonder if we have to resurrect the old wow64_respawn_p= rocess function for this border case" Along these lines, is anybody here still running a 64 bit Windows 10 which has *NOT* been updated to 1511? If so, I just need the output of a call to `cat /proc/self/maps' once for comparison. Thanks in advance, Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --l76fUT7nc3MelDdI Content-Type: application/pgp-signature Content-length: 819 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWX215AAoJEPU2Bp2uRE+gsW8P/RkQ/qzEigjryfIz9yTI0nRb Wo4hRQrEIUbAFk7lB6BxCAhssf1RI7mrE9zW6eq3YXb4GL7oAlQdaLGy/961H/Hg AEbHlTnPc75a03URJuiHecDjALqEhVdprzyI3C3Ds07C6p702pZw99tBhytjBRdi saqc4a1J+BmkNKkaceYUr9G7kO6kV7OWa2Z3bJmXS3iV87ZdJY1+LYg0JwBhNBnZ x5k6q+Aaeg4BTij9pgcnfXpC3zijLBghYmqaD8ETS+8EIXjDfKIQIXSfrZvn+Xev ZVNXqR9bv2uJRrHfja33/IfR32hLQxcSvs5hNe9dFDiKS7zBBVwVC1m6x5asVMgK AiqXutyS4Qkrz3fTctb8wzZARjvqvbtOzHlF1QeI1WdvKm0U3SSOzgBG14Jj33p1 4dLUYJAk0ELCxQxr1pY7Kva9JMxwDg/+PCDR84npkoDLDQM8PhJ92VG9IgsqeBKc OihrtiM+xljZxp6jlkD82YHbIv7tJWRIaBLHabbNnMuEsteMWk6iFDD59xEGfy+J gzEERPhzMdIao8HAkgSVuVZTxOydkyhveWdXRyNjXgFdBZzymqpjXIdArw8DBLux hoURiyJTt+PKu3fPcX5Mcs0Sep7TrdfTVdkjjWQrl8C9Yy2VFjPHzLt3cMbXRG2u 8XszDJ0GGPZX4z5gkh/4 =i23D -----END PGP SIGNATURE----- --l76fUT7nc3MelDdI--