This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: GREP: Memory Exhausted
- From: Dave Korn <dave dot korn dot cygwin at googlemail dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 12 May 2009 03:42:15 +0100
- Subject: Re: GREP: Memory Exhausted
- References: <28A2EAFEF380B447AF9E3FBFA6387D3189704E525F@AA-EXMSG-C425.southpacific.corp.microsoft.com> <4A08ACDE.9050805@gmail.com> <20090512010309.GA8065@ednor.casa.cgf.cx>
Christopher Faylor wrote:
> 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
Well, I couldn't trigger any kind of anomalous memory behaviour from
grepping through a few gigs of binary data with Cygwin grep-2.5.3-1; usage
stayed rock steady at around 3.5MB. So I took a guess that Shailesh might
have had the same problem that was giving me the same symptom. Maybe with a
bit of luck we can get the console fixed, you never know.
cheers,
DaveK
--
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/