Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Cause:
For some regular expressions DFA analysis can insert up to double "positions" than there are leaves.
Consequence:
There are not enough room to insert all the positions which may lead to crash for some REs.
Fix:
Space allocation for twice as many positions as there are leaves.
Result:
Enough space, no crash.
Cloning, since RHEL 6 is also impacted by this bug.
+++ This bug was initially created as a clone of Bug #713328 +++
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 6479 bytes
cmdline: grep --color=auto -Eq '(^| )*( |$)'
component: grep
Attached file: coredump, 393216 bytes
crash_function: __libc_message
executable: /bin/grep
kernel: 2.6.35.13-92.fc14.x86_64
package: grep-2.8-1.fc14
rating: 4
reason: Process /bin/grep was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1308101349
uid: 14986
How to reproduce
-----
1. grep -Eq '(^| )*( |$)'
2.
3.
--- Additional comment from eblake on 2011-06-14 19:31:00 MDT ---
Created attachment 504787[details]
File: backtrace
--- Additional comment from jskarvad on 2011-06-20 03:39:47 MDT ---
Upstream commit fixing the issue:
http://git.savannah.gnu.org/cgit/grep.git/commit/?id=0b91d6928e9d098d3746ce9f4bb4160a2e685f5c
--- Additional comment from updates on 2011-06-20 05:54:45 MDT ---
grep-2.8-4.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/grep-2.8-4.fc15
--- Additional comment from updates on 2011-06-20 05:57:55 MDT ---
grep-2.8-2.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/grep-2.8-2.fc14
--- Additional comment from updates on 2011-06-21 11:42:57 MDT ---
Package grep-2.8-2.fc14:
* should fix your issue,
* was pushed to the Fedora 14 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing grep-2.8-2.fc14'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/grep-2.8-2.fc14
then log in and leave karma (feedback).
Comment 2RHEL Program Management
2011-07-06 00:07:31 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.
Comment 3Jaroslav Škarvada
2012-02-28 12:55:25 UTC
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-2013-0977.html