From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17104 invoked by alias); 1 Dec 2015 14:01:09 -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 17090 invoked by uid 89); 1 Dec 2015 14:01:08 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-5.4 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 X-HELO: calimero.vinschen.de Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 01 Dec 2015 14:01:07 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 4753BA805D4; Tue, 1 Dec 2015 15:01:05 +0100 (CET) Date: Tue, 01 Dec 2015 14:01: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: <20151201140105.GW2755@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> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="cX4WM3qIY/fHWHDu" Content-Disposition: inline In-Reply-To: <565D8D88.4080601@gmail.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-SW-Source: 2015-12/txt/msg00010.txt.bz2 --cX4WM3qIY/fHWHDu Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 768 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. >=20 > 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, then 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 :( Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --cX4WM3qIY/fHWHDu Content-Type: application/pgp-signature Content-length: 819 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWXaghAAoJEPU2Bp2uRE+gQbUP/2Jb7QBTWXq5qzXE71F+Baqb fIhTuid7sL8xJW4KzFlORyH/vrrZgZJQZmVHLnbGT7f6v69Xs6AO4sPGoFDE4Ipl ir/ERFSaAwaDx486gC2vDrfGmHJ5GM3VB7Cb4Xkg7aO1bpVzxkieGVT01Pnvhcfu 9auy841beIw1hpmefGHg2LGYVkg/hjQ3Lsf3mI9HO6aTP7rQbWFpWKUtQRBVhIsB fPtp1C4tkZRe9hTWv4id1HVal4d6x9Z/K26XUGnK/4MwZ21DJV3etdxHn+9s1FFn 9ImD+g0a3LPPSz6TbeiRXdXOEg8y2tOMa2Q3zaulSFthMcmj5o+Vu8Zh62DiGLKf OmG0Ao4Uymjz3jgwFCWHpFEliw8mLMkKRixKv4e0SBD0tBqAsPWMnc6zshyVODCB y/zs0JjtahrsyQbcNXcR1UwhyE16y6VS7ryAFESyVlZudxSaZEBLffDI4TbqiMt/ sF7XzcJjv2G7HqPZxle+KQrl/g2oClAkSicNkZ+sSuAd5o3uUZwyC0ZpuD5S5pe/ Pm2+WGFaaoDO9sUuZrC6chZBPLx+aekB+W5q0k5D40+VdFE87WdUbmGu2Gzofsz0 X8ly0gPooe6ETKxZBB4B9Me7TEeNgBxSfCIV0j5x4b6nv807P22sd5HVx32tiBhk KoAM6ElXVs6j5OTMAlHk =bj4d -----END PGP SIGNATURE----- --cX4WM3qIY/fHWHDu--