[apport] w3m crashed with SIGSEGV when using g shortcut

Bug #123876 reported by Sitsofe Wheeler on 2007-07-03
Affects Status Importance Assigned to Milestone
w3m (Ubuntu)

Bug Description

Binary package hint: w3m

Description of the problem:
A segfault often happens if you laod a particular page while holding key, do a find then press g.

Steps to reproduce:
1. Start a gnome-terminal .
2. Type
w3m https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/121228
3. Before the page appears start holding down the right arrow on the keyboard.
4. Once page has fully loaded press the following:

Expected results:
Cursor to move to top right hand corner of the page.

Actual result:

How reproducible is the problem?
The problem is reproducible most of the time.

Version information:
Ubuntu 7.04
 w3m 0.5.1-5.1ubuntu1

ProblemType: Crash
Architecture: i386
Date: Tue Jul 3 23:11:53 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/w3m
Package: w3m 0.5.1-5.1ubuntu1
PackageArchitecture: i386
ProcCmdline: w3m https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/121228
ProcCwd: /var/crash
Signal: 11
SourcePackage: w3m
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
Uname: Linux galvatron 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video
 Segfault happened at: 0xb7c4fad6: mov %ecx,0x8(%esi)
 PC (0xb7c4fad6) ok
 source "%ecx" ok
 destination "0x8(%esi)" (0x00000008) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA

Sitsofe Wheeler (sitsofe) wrote :

StacktraceTop:_int_malloc () from /lib/tls/i686/cmov/libc.so.6
malloc () from /lib/tls/i686/cmov/libc.so.6
__add_to_environ () from /lib/tls/i686/cmov/libc.so.6
setenv () from /lib/tls/i686/cmov/libc.so.6
set_environ (var=0x82428d8 "", value=0x1c1 <Address 0x1c1 out of bounds>) at local.c:206

Changed in w3m:
importance: Undecided → Medium
status: New → Triaged
Sitsofe Wheeler (sitsofe) wrote :

Still here in Hardy. Step 3 no longer seems to be required and the problem is now reproducible every time.

Version information:
Ubuntu hardy (development branch)
w3m 0.5.1-5.1ubuntu1

Sitsofe Wheeler (sitsofe) wrote :

still here in Jaunty.

Version information:
Ubuntu 9.04
w3m 0.5.2-2build1

Kees Cook (kees) on 2009-09-16
description: updated
Sitsofe Wheeler (sitsofe) wrote :

Still here in Karmic.

Version information:
Ubuntu 9.10 (karmic)
w3m 0.5.2-2ubuntu1

Sitsofe Wheeler (sitsofe) wrote :

Nowadays I can't reproduce it on earlier versions of Ubuntu (where the problem was definitely occurring), nor in Lucid. Let's just close this as nearly two years is a long enough time and no one really develops w3m these days anyway...

Changed in w3m (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers