Bug 643235

Summary: [abrt] bash-4.1.7-1.fc13: yyparse: Process /bin/bash was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: mdeliberto
Component: bashAssignee: Roman Rakus <rrakus>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: rrakus, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:8f73ad2ad05468f4d9fd243d0e09601d4e1aa55d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-10-15 11:32:37 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 mdeliberto 2010-10-15 02:45:08 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: bash
component: bash
crash_function: yyparse
executable: /bin/bash
kernel: 2.6.34.7-56.fc13.x86_64
package: bash-4.1.7-1.fc13
rating: 4
reason: Process /bin/bash was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1287081383
uid: 500
Comment 1 mdeliberto 2010-10-15 02:45:11 UTC 
Created attachment 453613 [details]
File: backtrace
Comment 2 Roman Rakus 2010-10-15 11:06:30 UTC 
Can you please provide some steps to reproduce? Did you use hibernation?
Comment 3 mdeliberto 2010-10-15 11:14:50 UTC 
Did not use hibernation. It happened out the blue, I have been unable to reproduce it.
Comment 4 Roman Rakus 2010-10-15 11:32:37 UTC 
When you will have some reproducer, feel free to reopen this bug.