From: Michael DePaulo <mikedep333@gmail.com>
To: Rich Eizenhoefer <riche@microsoft.com>,
The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: From Microsoft: Windows 10 Console and Cygwin
Date: Wed, 29 Apr 2015 23:43:00 -0000 [thread overview]
Message-ID: <CAMKht8h5EwCtHe4cY69btH9Pcci-zG=PZCRFpVHZ-Qcx2QC1QQ@mail.gmail.com> (raw)
In-Reply-To: <20150429200616.GL3657@calimero.vinschen.de>
Hi, see bottom post.
On Wed, Apr 29, 2015 at 4:06 PM, Corinna Vinschen
<corinna-cygwin@cygwin.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
next prev parent reply other threads:[~2015-04-29 23:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 19:01 Rich Eizenhoefer
2015-04-29 19:50 ` Tim Prince
2015-04-29 20:06 ` Corinna Vinschen
2015-04-29 21:31 ` Rich Eizenhoefer
2015-04-30 8:22 ` Corinna Vinschen
2015-05-01 19:29 ` Rich Eizenhoefer
2015-05-02 13:47 ` Corinna Vinschen
2015-05-04 22:35 ` Rich Eizenhoefer
2015-05-05 8:22 ` Michael DePaulo
2015-05-31 20:07 ` Ismail Donmez
2015-06-01 8:24 ` Corinna Vinschen
2015-06-01 20:27 ` Rich Eizenhoefer
2015-06-02 7:56 ` Corinna Vinschen
2015-06-02 8:10 ` İsmail Dönmez
2015-06-02 16:37 ` Rich Eizenhoefer
2015-06-02 16:50 ` Corinna Vinschen
2015-06-02 17:50 ` Rich Eizenhoefer
2015-06-02 19:20 ` Eric Blake
2015-06-02 20:36 ` Vince Rice
2015-06-02 20:49 ` Warren Young
2015-06-08 11:49 ` Corinna Vinschen
2015-06-08 17:23 ` Rich Eizenhoefer
2015-04-29 23:43 ` Michael DePaulo [this message]
2015-04-30 7:56 ` Corinna Vinschen
2015-04-30 11:27 ` LRN
2015-04-30 12:44 ` Tony Kelman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMKht8h5EwCtHe4cY69btH9Pcci-zG=PZCRFpVHZ-Qcx2QC1QQ@mail.gmail.com' \
--to=mikedep333@gmail.com \
--cc=cygwin@cygwin.com \
--cc=riche@microsoft.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).