Date: Sun, 3 May 2009 23:39:21 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [1.7] Weird error "grep: writing output: Cannot allocate 	memory"
Message-ID: <20090504033921.GA6162@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <49FB714A.4010002@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <49FB714A.4010002@gmail.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Fri, May 01, 2009 at 11:01:46PM +0100, Dave Korn wrote:
>
>    Hi[ppo],
>
>  I've been seeing these odd error messages scattered in amongst my grep
>output occasionally of late, and decided to spend some time tracking them
>down.  It now seems to me that something very strange is going on with
>WriteConsoleW, as called from fhandler_console::write_normal().  This is
>possibly the same underlying bug that might explain why even a non-cygwin grep
>might show the problems documented in the earlier thread[*], although it's
>also possible that there were two separate issues cropping up there, of which
>this is one and the other was some kind of regex backtracking/recursion memory
>explosion.
>
>  The attached STC reproduces the problem, and apparently:
>
>gcc-3 -mno-cygwin stc.c -o stc -W -Wall -g -O0 -o stc-mingw.exe
>
>gcc-4 stc.c -o stc -W -Wall -g -O0
>
>.. it is cygwin independent, since both executables produce similar results:

A test case which demonstrates a failing Windows call fail isn't really
interesting as far as Cygwin is concerned.  Do you have a stc which
fails using Cygwin's API?

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/