This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [1.7] Weird error "grep: writing output: Cannot allocate memory"

Christopher Faylor wrote:
> On Sun, May 03, 2009 at 11:39:21PM -0400, Christopher Faylor wrote:
>> On Fri, May 01, 2009 at 11:01:46PM +0100, Dave Korn wrote:

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

  Well, just to state the obvious, Cygwin itself is written using Windows
calls, and if they are prone to fail it needs to be written to take that into
account.  As I guess you reached the similar conclusion.

> Do you have a stc which fails using Cygwin's API?

  I should be able to generate one.

> I made some changes to Cygwin's always-burgeoning console code which limit
> the number of characters transferred to the console.  Could you check if
> it still fails with these changes?

  I'll get to this during today, thanks.


Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]