This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: GREP: Memory Exhausted
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 11 May 2009 21:03:10 -0400
- Subject: Re: GREP: Memory Exhausted
- References: <28A2EAFEF380B447AF9E3FBFA6387D3189704E525F@AA-EXMSG-C425.southpacific.corp.microsoft.com> <4A08ACDE.9050805@gmail.com>
- Reply-to: cygwin at cygwin dot com
On Mon, May 11, 2009 at 11:55:26PM +0100, Dave Korn wrote:
>Some weeks ago... Shailesh Dadure wrote:
>>I am a support engineer from Microsoft trying to help my Customer
>>Maziyar Samadzadeh. We have been notified by Maziyar that when they
>>perform a Query on a bigger database using GREP we get the following
>>error
>>
>>GREP: Memory Exhausted
>
>Just to tie up the loose ends of this thread, which kind of petered out
>without any resolution: I've now notified Shailesh off-list about the
>apparent bug we uncovered in the WriteConsole API(*), and suggested he
>show the testcase around internally at Microsoft. I'll keep the list
>posted if anything interesting transpires.
It didn't really peter out. This is a well-known problem even on linux
where it is trivially easy to trigger. It doesn't necessarily have
anything to do with the console.
http://www.cygwin.com/ml/cygwin/2009-04/msg00374.html
--
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/