grep - Bugs: bug #29394, Incorrect matches with grep -w
You are not allowed to post comments on this tracker with your current authentication level.
bug #29394: Incorrect matches with grep -w
Submitter: | None | ||
Submitted: | Wed 31 Mar 2010 12:30:47 PM UTC | ||
Category: | None | Severity: | 3 - Normal |
Item Group: | None | Status: | Invalid |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Closed |
Wed 31 Mar 2010 07:20:33 PM UTC, comment #2: |
Dick Streefland <dicks> |
Wed 31 Mar 2010 04:30:30 PM UTC, comment #1: I cannot reproduce it on Fedora (Red Hat patched 2.5.3) or 2.6.x.
|
Paolo Bonzini <bonzini> |
Wed 31 Mar 2010 12:30:47 PM UTC, original submission:
In some situations, grep (and egrep) return incorrect results when the -w option is used. Example:
|
Anonymous |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 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 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2010-04-01 | bonzini | Status | None | Invalid | |
Open/Closed | Open | Closed |
Powered by Savane 3.13-758e.
Corresponding source code
It looks like the bug is not in the original grep, but in a Debian (and Ubuntu) patch. I compiled version 2.5.4 from the original sources, and it doesn't show the problem. When I revert 65-dfa-optional.patch in the Debian package, the problem disappears. I guess I should file a bug report with Debian instead...