Christopher Faylor wrote:
> You apparently haven't taken the advice of googling the problem.
Sure I did.
http://img23.imageshack.us/img23/8914/sureidid.png
Those links didn't go purple all by themselves.
> It
> really is very easy to trigger on linux.
Which of the many different bugs
;>>> 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 thi
ey
>>> 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
ase 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 WriteCo
Some weeks ago... 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
&g
On Wed, April 15, 2009 12:46 pm, Dave Korn wrote:
> Letters in an error message don't just randomly change between upper and
> lower case for no reason. Either you two are using different versions of
> grep, or Shailesh did not accurately report the *actual* error message
> that he was *actually*
>> Letters in an error message don't just randomly change between upper and
>> lower case for no reason.
>
> It just prints argv[0], so if you invoke it as GREP it will report as
> GREP, thanks to case insensivity.
ps: Sorry, of course that doesn't account for "Memory Exhausted" being
uppercase.
> Shailesh Dadure wrote:
>
>> GREP: Memory Exhausted
>
> Andy Hall wrote:
>
>> grep: memory exhausted
>
> Letters in an error message don't just randomly change between upper and
> lower case for no reason.
It just prints argv[0], so if you invoke it
On Wed, Apr 15, 2009 at 08:46:52PM +0100, Dave Korn wrote:
>Shailesh Dadure wrote:
>>GREP: Memory Exhausted
>
>Andy Hall wrote:
>
>>grep: memory exhausted
>
>Letters in an error message don't just randomly change between upper
>and lower case for no reaso
Shailesh Dadure wrote:
> GREP: Memory Exhausted
Andy Hall wrote:
> grep: memory exhausted
Letters in an error message don't just randomly change between upper and
lower case for no reason. Either you two are using different versions of
grep, or Shailesh did not accurately report
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
Reformatted--please read:
http://www.cygwin.com/acronyms/#TOFU
http://www.cygwin.com/acronyms/#PCYMTWLL
On 2009-04-14 15:35Z, Shailesh Dadure wrote:
>
[Corinna Vinschen wrote:]
>> Consequentially the bug report should go to the grep bug reporting
>> mailing list which you can find in the BUGS
-Original Message-
From: Corinna Vinschen [mailto:corinna-cyg...@cygwin.com]
Sent: 14 April 2009 19:11
To: cygwin@cygwin.com
Cc: Shailesh Dadure
Subject: Re: GREP: Memory Exhausted
On Apr 14 19:36, Shailesh Dadure wrote:
> Hello All,
>
> I am a support engineer from Microsoft tryin
Christopher Faylor wrote:
> 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 t
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 b
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 yo
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
On Apr 14 19:36, 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
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
GREP: Memory Exhausted
We have figured that at one point during the Query
19 matches
Mail list logo
