X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.2 required=5.0 tests=AWL,BAYES_00
X-Spam-Check-By:	sourceware.org
X-VirusChecked:	Checked
X-Env-Sender:	A DOT Hall AT servicepower DOT com
X-Msg-Ref:	server-4.tower-66.messagelabs.com!1239814792!36210325!1
X-StarScan-Version:	6.0.0; banners=-,-,-
MIME-Version:	1.0
Subject:	RE: GREP: Memory Exhausted
Date:	Wed, 15 Apr 2009 12:58:36 -0400
Message-ID:	<0FF3B6512477714C939F9B6310F6F97A02DEC78C@loui-dc1.sp.servicepower.com>
In-Reply-To:	<20090414151445.GA25210@ednor.casa.cgf.cx>
References:	<28A2EAFEF380B447AF9E3FBFA6387D3189704E525F AT AA-EXMSG-C425 DOT southpacific DOT corp DOT microsoft DOT com> <49E4A2A0 DOT 6090704 AT gmail DOT com> <49E4A198 DOT 4080408 AT bmts DOT com> <20090414151445 DOT GA25210 AT ednor DOT casa DOT cgf DOT cx>
From:	"Andy Hall" <A DOT Hall AT servicepower DOT com>
To:	<cygwin AT cygwin DOT com>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

I get this error all the time from simple recursive greps on large
source directory trees.   E.g.

$ grep -r zap *
Binary file SDE/BUILD_DBG/dist/ship.tar matches
Binary file SDE/BUILD_DBG/ship/lib/servlet-api.jar matches
grep: memory exhausted

$ grep --version
GNU grep 2.5.3

Copyright (C) 1988, 1992-2002, 2004, 2005  Free Software Foundation,
Inc.
This is free software; see the source for copying conditions.  There is
NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.

The same grep on Linux or Solaris usually works, but I think only
because virtual memory is handled differently.=20

If you watch memory consumption on windows while grep is running, it
remains flat for about 30 seconds and then starts growing in sizeable
chunks until it fails.=20=20

And BTW, there was an earlier version of grep that worked but I have
since lost the version number.

Andy Hall


> -----Original Message-----
> From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com] On
Behalf
> Of Christopher Faylor
> Sent: Tuesday, April 14, 2009 8:15 AM
> To: cygwin AT cygwin DOT com
> Subject: Re: GREP: Memory Exhausted
>=20
> On Tue, Apr 14, 2009 at 10:45:44AM -0400, Ralph Hempel wrote:
> > Dave Korn wrote:
> >> Shailesh Dadure wrote:
> >>> Hello All,
> >>>
> >>> 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
> >>   Would you like to use one of your two free phone support
incidents on
> >> this
> >> request, or will you be paying by credit or debit card for a paid
> support
> >> ticket?
> >
> > Geez Dave. I was going to suggest rebooting the machine to see if
that
> > changed anything, and then upgrading to Windows 7. But then I
thought
> > that it might be taken the wrong way...
> >
> > And why would anyone query a database using GREP?
>=20
> And a followup question:  Is it really Cygwin's grep?  The error
message
> looks
> suspicious.
>=20
> cgf
>=20
> --
> 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/


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

- Raw text -