From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 111454 invoked by alias); 29 Apr 2015 19:50:23 -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 111440 invoked by uid 89); 29 Apr 2015 19:50:22 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=4.1 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_MXURI,RCVD_IN_DNSWL_NONE,SPF_PASS,T_RP_MATCHES_RCVD autolearn=no version=3.3.2 X-HELO: omr-m03.mx.aol.com Received: from omr-m03.mx.aol.com (HELO omr-m03.mx.aol.com) (64.12.143.77) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Wed, 29 Apr 2015 19:50:21 +0000 Received: from mtaout-mbb01.mx.aol.com (mtaout-mbb01.mx.aol.com [172.26.254.109]) by omr-m03.mx.aol.com (Outbound Mail Relay) with ESMTP id EB4C77003709B for ; Wed, 29 Apr 2015 15:50:18 -0400 (EDT) Received: from [192.168.0.4] (cpe-71-79-8-193.cinci.res.rr.com [71.79.8.193]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mtaout-mbb01.mx.aol.com (MUA/Third Party Client Interface) with ESMTPSA id B4EBD38000097 for ; Wed, 29 Apr 2015 15:50:18 -0400 (EDT) Message-ID: <554135F9.3040407@aol.com> Date: Wed, 29 Apr 2015 19:50:00 -0000 From: Tim Prince Reply-To: tprince@computer.org User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: From Microsoft: Windows 10 Console and Cygwin References: In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit x-aol-global-disposition: G x-aol-sid: 3039ac1afe6d554135fa24ea X-AOL-IP: 71.79.8.193 X-SW-Source: 2015-04/txt/msg00627.txt.bz2 On 4/29/2015 3:01 PM, 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" > > 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 > > -- > Windows 10 has given me satisfactory results with cygwin64 (although I'm more likely to run git under 8.1). This is a welcome change from the days when Microsoft personnel stated that bugs reported primarily by cygwin users would not be fixed even when they could be reproduced outside cygwin. -- Tim Prince -- 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