Bug 551982 - SIGSEGV running /usr/bin/gnochm
Summary: SIGSEGV running /usr/bin/gnochm
Keywords:
Status: CLOSED DUPLICATE of bug 552417
Alias: None
Product: Fedora
Classification: Fedora
Component: gnochm
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Haïkel Guémar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e16fc23207a0e33fde40d6957a1...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-03 13:38 UTC by Jens Maucher
Modified: 2010-01-04 23:40 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-01-04 23:40:59 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
coredump.tar.bz2 (3.56 MB, application/x-bzip)
2010-01-04 21:53 UTC, Jens Maucher 		no flags Details
View All

Description Jens Maucher 2010-01-03 13:38:04 UTC 
abrt 1.0.0 detected a crash.

How to reproduce
-----
1. Opening a *.chm file
2. Click on a link from a chapter



cmdline: /usr/bin/python /usr/bin/gnochm /home/jensm/.aMule/Incoming/rhce5.RHCE.Red.Hat.Certified.Engineer.Linux.Study.Guide.(Exam.RH302),.Fifth.Edition.chm
component: python
executable: /usr/bin/python
kernel: 2.6.31.9-174.fc12.x86_64
package: python-2.6.2-2.fc12
rating: 3
reason: Process was terminated by signal 11
Comment 1 Dave Malcolm 2010-01-04 20:39:29 UTC 
Thank you for the bug report.

Unfortunately, without a stack trace from the crash it is impossible to determine what caused the crash. Please see http://fedoraproject.org/wiki/StackTraces for more information about getting a useful stack trace with debugging symbols. Even if you cannot reproduce this crash at will, you can prepare your system now to produce a good stack trace the next time you experience the crash. 

Thank you.
Comment 2 Jens Maucher 2010-01-04 21:53:07 UTC 
Created attachment 381661 [details]
coredump.tar.bz2

I attached the cordump, hope it helps.

-- Jens
Comment 3 Jens Maucher 2010-01-04 23:14:59 UTC 
I updated abrt, and reproduce the error again and opened a new bug with the complete informations.

New bug: #552417
Comment 4 Jens Maucher 2010-01-04 23:40:59 UTC 

*** This bug has been marked as a duplicate of bug 552417 ***
Note You need to log in before you can comment on or make changes to this bug.