Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 227417 - grep -F -i --line-regexp returns incorrect results on a simple file
Summary: grep -F -i --line-regexp returns incorrect results on a simple file
Alias: None
Product: Fedora
Classification: Fedora
Component: grep
Version: 6
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Stepan Kasal
QA Contact:
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2007-02-05 21:14 UTC by shez
Modified: 2008-05-06 19:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-05-06 19:10:13 UTC

Attachments (Terms of Use)

Description shez 2007-02-05 21:14:08 UTC
Description of problem:
grep -F --line-regexp returns incorrect results on a simple file.

Version-Release number of selected component (if applicable):

How reproducible:
grep -F -i --line-regexp -f  /tmp/test.txt /tmp/test.txt
test.txt contains:

Not all of the lines are returned, which they should be.  This works correctly 
in grep-2.5.1-31

Comment 1 Nick Lamb 2007-02-06 10:41:03 UTC
With version grep-2.5.1-54.1.2.fc6 on Fedora Core 6...

Works as intended in 'C' locale, but some lines are not returned in locale
'en_GB.UTF-8'. Specifically the LC_CTYPE locale setting influences this bug, so
maybe it's caused by misuse of one or more C library character type functions or
macros like the isspace() family.

Comment 2 Matthew Miller 2007-04-10 19:35:36 UTC
This was misfiled against FC4. Moving.

Comment 3 Stepan Kasal 2007-11-06 15:01:06 UTC
Verified that the bug still exists in 2.5.1-57.fc7.
Added -i to the summary of the bug; fgrep works without that.

Comment 4 Bug Zapper 2008-04-04 06:06:31 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here: to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out

Comment 5 Bug Zapper 2008-05-06 19:10:11 UTC
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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