Bug 610060

Summary: [abrt] crash in grep-2.6.3-1.fc12: elf_machine_rel_relative: Process /bin/grep was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Jayrome <jayrome>
Component: glibcAssignee: Andreas Schwab <schwab>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: jakub, jskarvad, lkundrak, schwab
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:e04a67e4d2e5b1768446168839751e45e1012317
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-23 10:35:23 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:
Attachments:
Description Flags
File: backtrace none

Description Jayrome 2010-07-01 13:35:14 UTC 
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: grep -c -w p4.clockmod
component: grep
crash_function: elf_machine_rel_relative
executable: /bin/grep
global_uuid: e04a67e4d2e5b1768446168839751e45e1012317
kernel: 2.6.32.14-127.fc12.i686
package: grep-2.6.3-1.fc12
rating: 4
reason: Process /bin/grep was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Comment 1 Jayrome 2010-07-01 13:35:20 UTC 
Created attachment 428419 [details]
File: backtrace
Comment 2 Jaroslav Škarvada 2010-07-27 08:05:26 UTC 
Thanks for report. I am sorry, I cannot reproduce this and the backtrace seems not to be promising.

Please do you have steps/test_data for reproducing this?
Comment 3 Jayrome 2010-07-27 12:52:55 UTC 
Nope, sorry. I don't have any steps to reproduce.
Comment 4 Jaroslav Škarvada 2010-08-23 10:05:45 UTC 
Actually from the backtrace it hangs in rtld, thus it seems as glibc fault, I am reassigning.
Comment 5 Andreas Schwab 2010-08-23 10:35:23 UTC 
Probably bad hardware.