Bug 157964

Summary: Grep "Segmentation fault" using Perl regular expression
Product: [Fedora] Fedora Reporter: Robert Jackson <bugzilla>
Component: grepAssignee: Tim Waugh <twaugh>
Status: CLOSED UPSTREAM QA Contact: Mike McLean <mikem>
Severity: low Docs Contact:
Priority: medium    
Version: 3   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-05-19 12:02:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Robert Jackson 2005-05-17 14:27:22 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050416 Fedora/1.0.3-1.3.1 Firefox/1.0.3

Description of problem:
I was using grep with a Perl regular expression to find files containing blank lines, but with some whitespace (i.e. a tab or a space).

One file (from about 20) caused grep to Segmentation fault.  This file was unique from the others since the last line was empty (i.e. it has an additional newline at the end).

I found that creating a file with a single newline caused the same Segmentation fault.

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

How reproducible:

Steps to Reproduce:
1. echo "\n" > temp.txt
2. grep -P '^\s+$' temp.txt

Actual Results:  Segmentation fault

Expected Results:  No Segmentation fault

Additional info:

I tried the same command on serveral different Ferdora platforms, and all give the same Segmentation fault.  Specifically:

RedHat Linux 9 (i686)
Fedora Core 1 (i686)
Fedora Core 3 (i686)
Fedora Core 3 (x86_64)

Comment 1 Tim Waugh 2005-05-19 12:02:14 UTC
I think this is something that has been addressed upstream, and which the next
GNU grep release will fix.

Comment 2 Tim Waugh 2005-06-28 08:16:59 UTC
*** Bug 161845 has been marked as a duplicate of this bug. ***

Comment 3 Tim Waugh 2005-06-28 09:36:42 UTC
*** Bug 161896 has been marked as a duplicate of this bug. ***