From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 122931 invoked by alias); 3 Dec 2015 19:09:24 -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 122915 invoked by uid 89); 3 Dec 2015 19:09:23 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=3.0 required=5.0 tests=AWL,BAYES_20,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 X-HELO: mout.kundenserver.de Received: from mout.kundenserver.de (HELO mout.kundenserver.de) (217.72.192.73) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Thu, 03 Dec 2015 19:09:22 +0000 Received: from [192.168.178.27] ([95.90.240.97]) by mrelayeu.kundenserver.de (mreue102) with ESMTPSA (Nemesis) id 0MBTfC-1ZxSFl0MJq-00AV1S for ; Thu, 03 Dec 2015 20:09:19 +0100 Subject: Re: fork issue when lauching cygwin64 process from 32bit native app on Windows 10 TH2 To: cygwin@cygwin.com References: <565D762E.4090109@gmail.com> <20151201112037.GU2755@calimero.vinschen.de> <565D8D88.4080601@gmail.com> <20151201140105.GW2755@calimero.vinschen.de> From: Thomas Wolff Message-ID: <56609361.6070609@towo.net> Date: Thu, 03 Dec 2015 19:09:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <20151201140105.GW2755@calimero.vinschen.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-UI-Out-Filterresults: notjunk:1;V01:K0:chDxD4iTsok=:IVg0RBUv41CYFyOg+hVs3K 4hAZDRb7I67NBD/kiJv9VhpW262TXOf8CqFyUH7RIGNxgzxc7RNh5a7xE9RYi2zpKYKg0oGcc hjUr3IpOKod/aqy2VwADKgIez/gd5V1kopyJd+8RmXCa2HqhOefeqbfHMB0mNW48qB0Zy15EW TNDxf0qWWjnkjOTd/bGuY6SMeht9MHOfo/X//ow4Htpg/qnb9SSToIb9SCY8PR74WjnGrs/Wj KnscIQ67w3y8TwCwDDwmr0ycPjw8ZGrg1Frw9z56nP5X4HMwe2rbmZa3fOZ9+0MPDuTGqSrLh LWrYKTnYFYF/I8cOzInOHe0kH11DpKA0Eok5sQbJ/U9VC/bfh99u/gv/1HHako6RF7ASBVZD3 sAyf5MtvI25k/uLsy/xPHFvyNxd3IEtfaLZBNyxELTrJcSwEOqfn5ALwVkJ/fqP5+AInSMmkO FtHH8gYr5n9bp/4ED8Trcmr1zZ5B50asZxTd1kf2s77K/lEhixAJYWqn2Ey7m9qaMM2MJWiht JzLb6J7S6/oFgcpml7D12wseoMNgHUl83hW68vhEmAiuA4CeCSNoSTpCb5C0n2h8ednRTy0/m UeB7cAOkZCLwc9gkcV2r4/aw96rzdg2SEVbyboC9zL0rpglrDcb4ey7Gld+v8JBlJ6PP6fiXV EfTHKLjb4mE5YMaKOmSp3lyC8Q/RMHawwhzU8Rdmowmixi8YlisJpu+rbXEwAYEjPq3j+/aG/ BOeCIGfT6K/e3A/5 X-IsSubscribed: yes X-SW-Source: 2015-12/txt/msg00037.txt.bz2 Am 01.12.2015 um 15:01 schrieb Corinna Vinschen: >> ... > 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 :( For reference, this has also been reported on https://github.com/mintty/mintty/issues/493 Thomas -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple