From: Rich Eizenhoefer <riche@microsoft.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: From Microsoft: Windows 10 Console and Cygwin
Date: Wed, 29 Apr 2015 19:01:00 -0000 [thread overview]
Message-ID: <BY1PR03MB1436C656CEF12387D40CD74EB4D70@BY1PR03MB1436.namprd03.prod.outlook.com> (raw)
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"
Please let me know if there are other problems you are experiencing with the W10 console that are a regression from previous versions. We are a small team, but we want to help where possible to ensure that Cygwin continues to run well in Windows 10.
Thanks,
Rich
--
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 reply other threads:[~2015-04-29 19:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 19:01 Rich Eizenhoefer [this message]
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
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=BY1PR03MB1436C656CEF12387D40CD74EB4D70@BY1PR03MB1436.namprd03.prod.outlook.com \
--to=riche@microsoft.com \
--cc=cygwin@cygwin.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).