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:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type
	:content-transfer-encoding; q=dns; s=default; b=fVWI82tW+IqqGtPw
	oeAPW00yfX08Qk8RwSIBNPdJC600jK5YEu4MvfCb5yq1rpj8G7rYKnQ6egKp2T9m
	LP/2gecFmwcB7Gda2vDMDhoB4Fz82yxHlzE/T6SDmfOKRHD7YArGStSZVFicoDs0
	yBrk8K/9Coe6fmh7DAZT/+HY9eM=
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:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type
	:content-transfer-encoding; s=default; bh=L2XqR/0np5x4NjyQg3PD5a
	TCL5w=; b=Z2ls0RxGqXgphdtbBDT0p0BT4Zdulb/YehvQoK8h/snSN3ewUpiG3q
	exzMIrXNSzqv3GrGGPWfQLPx/gEbm9M89xbqTagsb5vYp9X/PEqC/vKwdhu5I0b5
	kYnR6LaNvWtlTbchTL3iXnOJaVQBTpgwGBC5wMdgoc+H2WjG8Orms=
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.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	mail-lb0-f181.google.com
MIME-Version:	1.0
X-Received:	by 10.153.7.133 with SMTP id dc5mr1267461lad.17.1430350982493; Wed, 29 Apr 2015 16:43:02 -0700 (PDT)
In-Reply-To:	<20150429200616.GL3657@calimero.vinschen.de>
References:	<BY1PR03MB1436C656CEF12387D40CD74EB4D70 AT BY1PR03MB1436 DOT namprd03 DOT prod DOT outlook DOT com> <20150429200616 DOT GL3657 AT calimero DOT vinschen DOT de>
Date:	Wed, 29 Apr 2015 19:43:02 -0400
Message-ID:	<CAMKht8h5EwCtHe4cY69btH9Pcci-zG=PZCRFpVHZ-Qcx2QC1QQ@mail.gmail.com>
Subject:	Re: From Microsoft: Windows 10 Console and Cygwin
From:	Michael DePaulo <mikedep333 AT gmail DOT com>
To:	Rich Eizenhoefer <riche AT microsoft DOT com>,
	The Cygwin Mailing List <cygwin AT cygwin DOT com>
X-IsSubscribed:	yes
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id t3TNhM7I004496

Hi, see bottom post.

On Wed, Apr 29, 2015 at 4:06 PM, Corinna Vinschen
<corinna-cygwin AT cygwin DOT com> wrote:
> Hi Rich,
>
> nice to read from you.
>
> On Apr 29 19:01, Rich Eizenhoefer wrote:
>> Hi,
>>
>> I'm the Program Manager at Microsoft for the updated Windows 10
>> console. I searched the Cygwin FAQ and mailing list archives for
>> issues related to Windows 10 and found an item about multiple windows
>> which should already be fixed. We have received a couple reports about
>> crashes when running on Windows 10 with the new console enabled. For
>> example:
>>
>> "cygwin is dying when i run a bunch of the git tools. For example: >grep -rin log .\ 0 [main] us 0 init_cheap: VirtualAlloc pointer is null, Win32 error 487 AllocationBase 0x0, BaseAddress 0x68570000, RegionSize 0x3A0000, State 0x10000 C:\Program Files (x86)\Git\bin\grep.exe: *** Couldn't reserve space for cygwin's heap, Win32 error 0"
>
> This error message is a bit weird.  For one thing, it would be nice if
> you could give us a pointer to the message.  I'm not aware of such a bug
> report.
>
> Also, this is about a non-Cygwin version of git as the path to the git
> tools suggests.  On the other hand, if it's not a Cygwin version, the
> error message itself only makes marginal sense.  So maybe it's a Cygwin
> DLL as part of some third party package which is often outdated in
> relation to the official Cygwin distro version.
>
> As for the error message itself, it refers to the fact that, after a
> Cygwin fork() call, the forked child can't reserve the space required
> for the so-called "cygwin heap", a region used for internal usage
> especially important for fork/exec related stuff.  This usually points
> to Cygwin DLLs which are not rebased, or a non-Cygwin DLL loaded into a
> spot required for a Cygwin DLL after a fork.  This is especially a
> problem on 32 bit due to the restricted virtual memory.
>
> However, if I'm not completely off-track, the bug report does not really
> have anything to do with a bad interaction between the W10 console and
> Cygwin.  While my own W10 virtual machine under Qemu/KVM fails to update
> to versions after build 9926, I didn't encounter any unusual behaviour
> of the W10 console in comparison with, say, the W8.1 console yet.  I'm
> usually running Cygwin tools in mintty, but I did test the W10 console,
> too, of course.
[...]

Allow me to clarify.

"C:\Program Files (x86)\Git\" is "Git for Windows", AKA "msysgit":
https://msysgit.github.io/

As explained on README.md, it uses a MSys:
https://github.com/msysgit/msysgit

And as explained on that README.md, MSys is a fork of an old version of Cygwin.

MSys's home page is here, it is part of the MinGW project:
http://mingw.org/wiki/msys

-Mike

--
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 -