Bug 683753
Summary: | grep does not correctly handle unicode symbol property | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Petr Šplíchal <psplicha> | ||||
Component: | grep | Assignee: | Jaroslav Škarvada <jskarvad> | ||||
Status: | CLOSED ERRATA | QA Contact: | Martin Frodl <mfrodl> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 6.1 | CC: | fholec, jkejda, mfrodl, mnavrati, ohudlick, ovasik, pbonzini, ppisar, tlavigne | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
URL: | http://savannah.gnu.org/patch/?3934 | ||||||
Whiteboard: | |||||||
Fixed In Version: | grep-2.6.3-6.el6 | Doc Type: | Bug Fix | ||||
Doc Text: |
Previously, the grep utility did not request processing of UTF-8 from the Perl-compatible regular expressions (PCRE) library if a UTF-8 locale was in effect. As a consequence, Unicode symbols were not correctly matched if a Perl regular expression (the "-P" option) was used with a UTF-8 locale. This update adds a request for UTF-8 processing to the PCRE library, and grep now correctly handles Unicode symbols in the described situation.
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2014-06-04 09:03:20 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 947782 | ||||||
Attachments: |
|
Description
Petr Šplíchal
2011-03-10 10:00:57 UTC
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative. This is bug in grep. It does not request UTF-8 processing in pcre when running in UTF-8 locale. Current behavior is identical to ASCII mode: $ printf '/%s/\n%s\n' '\P{S}' '€' | ./pcretest PCRE version 8.31 2012-07-06 re> data> 0: \xe2 data> But it should run in UTF-8 mode: $ printf '/%s/8\n%s\n' '\P{S}' '€' | ./pcretest PCRE version 8.31 2012-07-06 re> data> No match data> The difference is the "/8" modifier. The PCRE API has PCRE_UTF8 option in pcre_compile(3) for that and grep should pass it to pcre_compile(3) when UTF-8 locale is in effect. Created attachment 606796 [details]
Proposed fIx
This is patch against development grep, it applies to 2.14 too.
There seems to be already an upstream report with different fix <http://savannah.gnu.org/patch/?3934>. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate, in the next release of Red Hat Enterprise Linux. (In reply to comment #4) Thanks. > There seems to be already an upstream report with different fix > <http://savannah.gnu.org/patch/?3934>. > Also linked to this BZ, waiting for upstream resolution. Fixed in upstream commit 003797b2d498fd16f67790a3c1129df9d0eb4722. (In reply to comment #7) > Fixed in upstream commit 003797b2d498fd16f67790a3c1129df9d0eb4722. Thanks. Fixed in grep-2.6.3-6.el6. Test is included, it is run during the compilation. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0622.html |