X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 	tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <4A08E207.1080402@gmail.com>
Date: Tue, 12 May 2009 03:42:15 +0100
From: Dave Korn <dave DOT korn DOT cygwin AT googlemail DOT com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: GREP: Memory Exhausted
References: <28A2EAFEF380B447AF9E3FBFA6387D3189704E525F AT AA-EXMSG-C425 DOT southpacific DOT corp DOT microsoft DOT com> <4A08ACDE DOT 9050805 AT gmail DOT com> <20090512010309 DOT GA8065 AT ednor DOT casa DOT cgf DOT cx>
In-Reply-To: <20090512010309.GA8065@ednor.casa.cgf.cx>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

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/