X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:references:from:to:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=X3t0zprqpucJwdnQ
	TCvI1ezzXeAVBQO0mNo2O952Du5Z5IEfoZEiUNDvTqALDrld3W/+2ATyaFMRgb5h
	xHUZXsRW13P387jlmAMmQnwm9Zb7wQO+Os7EQIBnGWVyJeQxDOyWX7q8GG34vPGc
	2dFOR3AEd6742khK2HO7UKfok8o=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:references:from:to:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=5TSC5XFjQXlnLfI/WR39wY
	qYW0c=; b=skC+42ZADcLVZH7SrHKRJVUtjJFR+djwrIev8bNPT74ku5UFh4b+FC
	E+XxEzNX90VIQA/qhFaT/nRPD6RMFzU45h5PSq0hxXAbnEAZ35UWL2RA21ELWq4J
	IO/bSlS7S0DYNnl/WoNusGwXLnl4RkWp4/+WZ/lE2yPVf93hL6qB4=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
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
Reply-To:	rob AT blaeu DOT com
Subject:	Re: fork issue when lauching cygwin64 process from 32bit native app on Windows 10 TH2
References:	<565D762E DOT 4090109 AT gmail DOT com> <20151201112037 DOT GU2755 AT calimero DOT vinschen DOT de> <565D8D88 DOT 4080601 AT gmail DOT com> <20151201140105 DOT GW2755 AT calimero DOT vinschen DOT de> <565DDB8E DOT 1090609 AT gmail DOT com>
From:	Rob van Eijk <rob AT blaeu DOT com>
Openpgp:	id=3F5BAB6A5672AF8AACAC86C454DBC270F0CB5B46
X-Enigmail-Draft-Status:	N1111
To:	cygwin AT cygwin DOT com
Message-ID:	<565DF5E8.5010908@blaeu.com>
Date:	Tue, 1 Dec 2015 19:32:56 +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>

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

- Raw text -