Bug 1210423 - pcregrep -o '(?<=\Ka)' does not halt
Summary: pcregrep -o '(?<=\Ka)' does not halt
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: pcre
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Pisar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-09 16:56 UTC by Petr Pisar
Modified: 2015-05-12 20:38 UTC (History)
3 users (show)

Fixed In Version: pcre-8.33-10.fc20
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1217084 (view as bug list)
Environment:
Last Closed: 2015-05-12 20:35:34 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Upstream fix for pcregrep ported to 8.36 (7.49 KB, patch)
2015-04-09 16:57 UTC, Petr Pisar
no flags Details | Diff
Upstream fix for pcretest ported to 8.36 (4.52 KB, patch)
2015-04-10 06:35 UTC, Petr Pisar
no flags Details | Diff

Description Petr Pisar 2015-04-09 16:56:40 UTC
This command never halts:

$ echo -n a | pcregrep  '(?<=\Ka)'

Fixed with upstream commit:

commit b4332d7dd831b3547b3f541495de4a79554e538e
Author: ph10 <ph10@2f5784b3-3f2a-0410-8824-cb99058d5e15>
Date:   Tue Apr 7 15:52:11 2015 +0000

    Fix pcregrep loop when \K is used in a lookbehind assertion.
    
    
    git-svn-id: svn://vcs.exim.org/pcre/code/trunk@1543 2f5784b3-3f2a-0410-8824-cb99058d5e15

Similar bug is in pcretest:

$ printf '%s\n%s\n' '/(?<=\Ka)/g+' 'aaaaa' | pcretest

Fixed with upstream commitL

commit c3579a7581cb8b3ca3c9617d63083afea29de646
Author: ph10 <ph10@2f5784b3-3f2a-0410-8824-cb99058d5e15>
Date:   Tue Apr 7 16:19:03 2015 +0000

    Fix pcretest loop for \K in lookbehind assertion.
    
    
    git-svn-id: svn://vcs.exim.org/pcre/code/trunk@1544 2f5784b3-3f2a-0410-8824-
cb99058d5e15

All Fedoras are affected.

Comment 1 Petr Pisar 2015-04-09 16:57:51 UTC
Created attachment 1012761 [details]
Upstream fix for pcregrep ported to 8.36

Comment 2 Petr Pisar 2015-04-10 06:35:32 UTC
Created attachment 1012980 [details]
Upstream fix for pcretest ported to 8.36

Comment 3 Fedora Update System 2015-04-10 07:13:06 UTC
pcre-8.36-5.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/pcre-8.36-5.fc22

Comment 4 Fedora Update System 2015-04-10 08:24:00 UTC
pcre-8.35-9.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/pcre-8.35-9.fc21

Comment 5 Fedora Update System 2015-04-10 14:00:42 UTC
pcre-8.33-9.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/pcre-8.33-9.fc20

Comment 6 Fedora Update System 2015-04-22 22:45:51 UTC
pcre-8.36-5.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 7 Fedora Update System 2015-04-24 06:53:46 UTC
pcre-8.35-10.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/pcre-8.35-10.fc21

Comment 8 Fedora Update System 2015-04-24 07:14:26 UTC
pcre-8.33-10.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/pcre-8.33-10.fc20

Comment 9 Fedora Update System 2015-04-26 12:55:48 UTC
Package pcre-8.33-10.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing pcre-8.33-10.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-6928/pcre-8.33-10.fc20
then log in and leave karma (feedback).

Comment 10 Fedora Update System 2015-05-12 20:35:34 UTC
pcre-8.35-10.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 11 Fedora Update System 2015-05-12 20:38:26 UTC
pcre-8.33-10.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.