Bug 643235 - [abrt] bash-4.1.7-1.fc13: yyparse: Process /bin/bash was killed by signal 11 (SIGSEGV)
Summary: [abrt] bash-4.1.7-1.fc13: yyparse: Process /bin/bash was killed by signal 11 ...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: bash
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Roman Rakus
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8f73ad2ad05468f4d9fd243d0e0...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-15 02:45 UTC by mdeliberto
Modified: 2014-01-13 00:12 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-10-15 11:32:37 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (195.74 KB, text/plain)
2010-10-15 02:45 UTC, mdeliberto 		no flags Details
View All

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.
Note You need to log in before you can comment on or make changes to this bug.