grep - Bugs: bug #9886, 'memory exhausted' error on very...
You are not allowed to post comments on this tracker with your current authentication level.
bug #9886: 'memory exhausted' error on very long lines
Submitter: | None | ||
Submitted: | Wed 04 Aug 2004 06:10:43 PM UTC | ||
Votes: | 150 | ||
Category: | None | Severity: | 3 - Normal |
Item Group: | None | Status: | Wont Fix |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Closed |
Fri 04 Dec 2009 07:46:35 PM UTC, comment #5: |
Paolo Bonzini <bonzini> |
Spam posted by dimon1 | |
Spam posted by scuko | |
Spam posted by dayatakoy | |
Fri 23 May 2008 09:35:57 AM UTC, comment #1: I've just tested this example. I've not got any error, but the memory usage was about 84% during execution. It seems to me that bug was fixed.
|
-Deleted Account- <scuko> |
Wed 04 Aug 2004 06:10:43 PM UTC, original submission:
I've seen discussions and various patches on the web for this problem, but I'm wondering why it hasn't been fixed within the main source tree. I'm trying search the output of strings run on a hard drive image (dd). The output from strings includes several very long lines. It seems that when grep hits these lines, it is unable to load the entire line into memory and dies.
|
Anonymous |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 150 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 5 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2009-12-04 | bonzini | Status | None | Wont Fix | |
Open/Closed | Open | Closed | |||
2007-05-18 | loisch | Carbon-Copy | - | Added loisch | |
2006-11-22 | twaugh | Carbon-Copy | - | Added twaugh | |
2005-04-11 | julianfoad | Summary | 'memory exhasted' error on very long lines | 'memory exhausted' error on very long lines |
Powered by Savane 3.13-f8d8.
Corresponding source code
grep is really a line-based tool, cannot fix this.