Bug 680355 - [abrt] w3m-0.5.2-18.fc14: wc_any_to_ucs: Process /usr/bin/w3m was killed by signal 11 (SIGSEGV)
Summary: [abrt] w3m-0.5.2-18.fc14: wc_any_to_ucs: Process /usr/bin/w3m was killed by s...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: w3m
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Parag Nemade
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:3bc0a185fbca0f3233ca05766c2...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-25 08:40 UTC by yohei2triton
Modified: 2011-03-29 07:53 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-29 07:53:12 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (21.40 KB, text/plain)
2011-02-25 08:40 UTC, yohei2triton 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description yohei2triton 2011-02-25 08:40:14 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 21909 bytes
cmdline: w3m /home/yohei/.w3m/home.html
component: w3m
Attached file: coredump, 9994240 bytes
crash_function: wc_any_to_ucs
executable: /usr/bin/w3m
kernel: 2.6.35.11-83.fc14.x86_64
package: w3m-0.5.2-18.fc14
rating: 4
reason: Process /usr/bin/w3m was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1298622851
uid: 500

How to reproduce
-----
1. back to previous buffer
2.
3.
Comment 1 yohei2triton 2011-02-25 08:40:16 UTC 
Created attachment 480951 [details]
File: backtrace
Comment 2 Parag Nemade 2011-02-25 09:35:59 UTC 
Can you please provide more information like which web page are you browsing and what triggers a crash?
Comment 3 yohei2triton 2011-02-25 10:13:56 UTC 
I do not remember which web page I was browsing.
I checked my history but I could not remember.
w3m crashed when I went back to previous web page.
Sorry for poor information.
Comment 4 Parag Nemade 2011-03-29 07:53:12 UTC 
I am still unable to reproduce this bug. Closing this now. If crash happens again please report it back.
Note You need to log in before you can comment on or make changes to this bug.