Bug 625613 - [abrt] yelp-2.30.1-1.fc13: __strchr_sse42: Process /usr/bin/yelp was killed by signal 11 (SIGSEGV)
Summary: [abrt] yelp-2.30.1-1.fc13: __strchr_sse42: Process /usr/bin/yelp was killed b...
Keywords:
Status: CLOSED DUPLICATE of bug 620286
Alias: None
Product: Fedora
Classification: Fedora
Component: yelp
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:901e55405c3cefebe34b8d1404e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-19 22:46 UTC by Paul W. Frields
Modified: 2010-11-09 16:55 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 16:55:15 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (42.94 KB, text/plain)
2010-08-19 22:46 UTC, Paul W. Frields 		no flags Details
View All

Description Paul W. Frields 2010-08-19 22:46:32 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: gnome-help ghelp:///usr/share/gnome/help/gnome-terminal/C/gnome-terminal.xml
comment: Crash on 'make' info page in yelp
component: yelp
crash_function: __strchr_sse42
executable: /usr/bin/yelp
kernel: 2.6.33.6-147.2.4.fc13.x86_64
package: yelp-2.30.1-1.fc13
rating: 4
reason: Process /usr/bin/yelp was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1282162916
uid: 500

How to reproduce
-----
1. Open yelp from menu (System > Help)
2. Choose GNU Info Pages from navigation at left
3. Choose GNU Packages (note the capital 'P' in Packages), and then select Make.

Note that 'info make' at CLI works OK as far as the user can tell.
Comment 1 Paul W. Frields 2010-08-19 22:46:34 UTC 
Created an attachment (id=439817)
File: backtrace
Comment 2 Karel Klíč 2010-11-09 16:55:15 UTC 

*** This bug has been marked as a duplicate of bug 620286 ***
Comment 3 Karel Klíč 2010-11-09 16:55:15 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #620286.

Sorry for the inconvenience.
Note You need to log in before you can comment on or make changes to this bug.