From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 84346 invoked by alias); 4 Dec 2015 16:35:21 -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 84337 invoked by uid 89); 4 Dec 2015 16:35:21 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.0 required=5.0 tests=AWL,BAYES_50,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: Ishtar.hs.tlinx.org Received: from ishtar.tlinx.org (HELO Ishtar.hs.tlinx.org) (173.164.175.65) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Fri, 04 Dec 2015 16:35:20 +0000 Received: from [192.168.4.12] (Athenae [192.168.4.12]) by Ishtar.hs.tlinx.org (8.14.9/8.14.4/SuSE Linux 0.8) with ESMTP id tB4GYrZV056349 for ; Fri, 4 Dec 2015 08:34:57 -0800 Message-ID: <5661C0AC.8050209@tlinx.org> Date: Fri, 04 Dec 2015 16:35:00 -0000 From: Linda Walsh User-Agent: Thunderbird MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: fork issue when lauching cygwin64 process from 32bit native app on Windows 10 TH2 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> In-Reply-To: <565DF5E8.5010908@blaeu.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2015-12/txt/msg00046.txt.bz2 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, 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 :( >> Yup. I can confirm. ---- Win10 has a 32-bit version? 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)? -- 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