Bug 575752

Summary: [abrt] crash in w3m-0.5.2-15.fc12: Process /usr/bin/w3m was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Robert Binkhorst <rbinkhor>
Component: w3mAssignee: Parag Nemade <pnemade>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: i18n-bugs, pnemade
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:94f636b14840fae853fa53bf99ab456456010f28
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-30 10:22:36 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 Robert Binkhorst 2010-03-22 10:42:28 UTC 
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: w3m -o indent_incr=0 -o multicol=false -o no_cache=true -o use_cookie=false -o display_charset=utf8 -o system_charset=utf8 -o follow_locale=false -o use_language_tag=true -o ucs_conv=true -T text/html -dump /home/rbinkhorst/buildroot/BUILD/xulrunner-1.9.0.10/mozilla/layout/generic/crashtests/323386-1.html
comment: No idea, it popped up in ABRT
component: w3m
executable: /usr/bin/w3m
kernel: 2.6.32.9-70.fc12.x86_64
package: w3m-0.5.2-15.fc12
rating: 4
reason: Process /usr/bin/w3m was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Comment 1 Robert Binkhorst 2010-03-22 10:42:31 UTC 
Created attachment 401694 [details]
File: backtrace
Comment 2 Parag Nemade 2010-05-24 09:21:51 UTC 
Are you still able to reproduce this?
Comment 3 Robert Binkhorst 2010-05-25 08:32:57 UTC 
I've not seen it dump core again, but maybe I just didn't trigger it. As I'm unsure why it crashed on me it's hard to say whether it's resolved or not... I guess since no-one else has attached to this BZ and it's not happened again you can close it and it will re-open if it happens again.
Comment 4 Parag Nemade 2010-05-25 08:37:24 UTC 
Actually few other people do found this bug but when asked them are you able to reproduce they said no.

So, it looks strange why it happened only once to all such bug reporters.