From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 99815 invoked by alias); 1 Dec 2015 19:33:04 -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 99712 invoked by uid 89); 1 Dec 2015 19:33:03 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.3 required=5.0 tests=BAYES_20,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 X-HELO: lb2-smtp-cloud6.xs4all.net Received: from lb2-smtp-cloud6.xs4all.net (HELO lb2-smtp-cloud6.xs4all.net) (194.109.24.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Tue, 01 Dec 2015 19:33:01 +0000 Received: from [192.168.1.100] ([83.163.15.68]) by smtp-cloud6.xs4all.net with ESMTP id oKYt1r0071U6Tez01KYxtA; Tue, 01 Dec 2015 20:32:58 +0100 Reply-To: rob@blaeu.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> From: Rob van Eijk Openpgp: id=3F5BAB6A5672AF8AACAC86C454DBC270F0CB5B46 X-Enigmail-Draft-Status: N1111 To: cygwin@cygwin.com Message-ID: <565DF5E8.5010908@blaeu.com> Date: Tue, 01 Dec 2015 19:33:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <565DDB8E.1090609@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-SW-Source: 2015-12/txt/msg00013.txt.bz2 Op 1-12-2015 om 17:40 schreef David Macek: > 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, 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. > I upgraded today to Windows 10 v1511. I ran into the same problem. I renamed my cygwin root directory (64 bit) and installed a 32 bit version of cygwin. The fork problem does not appear on the 32 bit version. In conclusion, I confirm that the issue appears when running a 32 bit version from a 64 bit cygwin. It does not appear when running a 32 bit app from a 32 bit cygwin. PS: my test applicatin is notepad++ with the nppexec plugin, which I use to power up the make command in a cygwin shell. mvg::Rob -- 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