grep - Bugs: bug #27275, Wrong behaviour with GREP_USE_DFA=0
You are not allowed to post comments on this tracker with your current authentication level.
bug #27275: Wrong behaviour with GREP_USE_DFA=0
Submitter: | None | ||
Submitted: | Tue 18 Aug 2009 09:03:34 AM UTC | ||
Category: | None | Severity: | 3 - Normal |
Item Group: | None | Status: | None |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Closed |
Wed 31 Mar 2010 07:50:51 PM UTC, comment #3: |
Dick Streefland <dicks> |
Fri 04 Dec 2009 12:20:00 PM UTC, comment #2: GREP_USE_DFA is not present in upstream grep (though it may be a good idea to add it). |
Paolo Bonzini <bonzini> |
Wed 19 Aug 2009 01:42:30 PM UTC, comment #1: Grep 2.5.4 uses both own DFA engine and regex engine included
|
Norihirio Tanaka <noritnk> |
Tue 18 Aug 2009 09:03:34 AM UTC, original submission:
From Debian bug #538737. I confirmed it with version 2.5.4
|
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.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2009-12-04 | bonzini | Open/Closed | Open | Closed |
Powered by Savane 3.13-758e.
Corresponding source code
Bug #29394 is another example where setting GREP_USE_DFA to 0 causes incorrect matches. I'm not sure if the (Debian) patch that adds the GREP_USE_DFA environment variable is to blame, or that there is a problem in the DFA engine.