X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-9.9 required=5.0 	tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_PASS
X-Spam-Check-By: sourceware.org
From: Shailesh Dadure <Shailesh DOT Dadure AT microsoft DOT com>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Date: Tue, 14 Apr 2009 23:35:56 +0800
Subject: RE: GREP: Memory Exhausted
Message-ID: <28A2EAFEF380B447AF9E3FBFA6387D3189704E5337@AA-EXMSG-C425.southpacific.corp.microsoft.com>
References: <28A2EAFEF380B447AF9E3FBFA6387D3189704E525F AT AA-EXMSG-C425 DOT southpacific DOT corp DOT microsoft DOT com>  <20090414134104 DOT GW15443 AT calimero DOT vinschen DOT de>
In-Reply-To: <20090414134104.GW15443@calimero.vinschen.de>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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

Hello Corinna,

Thank you for the reply, I was unable to find the information on mailing li=
st on the CYGWIN page. Is it some other location you are referring too?


Thanks and Regards,
Shailesh Dadure
Support Engineer=A0| Microsoft Enterprise Platform Support | Windows Server=
 Performance Team


-----Original Message-----
From: Corinna Vinschen [mailto:corinna-cygwin AT cygwin DOT com]=20
Sent: 14 April 2009 19:11
To: cygwin AT cygwin DOT com
Cc: Shailesh Dadure
Subject: Re: GREP: Memory Exhausted

On Apr 14 19:36, Shailesh Dadure wrote:
> Hello All,
>=20
> 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
>=20
> GREP: Memory Exhausted
>=20
> We have figured that at one point during the Query the application
> starts allocating memory drastically till we get this error. This
> happens probably within 30 seconds. On Further research we found that
> the GREP application has same behaviour on UNIX and LINUX environment.
> This seems to be same on Windows Environment too. However, in Windows
> the application cannot grow beyond 2GB so it crashes at that mark.
>=20
> Do we have any know issues with GREP. If Yes, has this been taken care
> in later updates? Please update us regarding the issue as soon as
> possible.

This is almost surely the wrong mailing list to report this problem.
Since you found that the Cygwin version of grep doesn't behave
differently than the Unix and Linux versions, it's apparently a generic
problem in grep.

Consequentially the bug report should go to the grep bug reporting
mailing list which you can find in the BUGS section of the grep man
page.  Btw., the BUGS section in the grep man page also contains some
interesting hints about situations which require lots of memory and=20
exponential time/space.


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat


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