GREP: Memory Exhausted

Dave Korn dave.korn.cygwin@googlemail.com
Tue May 12 02:31:00 GMT 2009


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/



More information about the Cygwin mailing list