htop crashed with SIGABRT

Bug #945013 reported by Thibaut Brandscheid
24
This bug affects 3 people
Affects Status Importance Assigned to Milestone
htop (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

During update process to precise beta 1 I monitored my old P4 PC with htop. After some time the program crashed unexpected, all I did was to change the view with 'F6' to 'sort by CPU'.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: htop 1.0-1
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686
ApportVersion: 1.94-0ubuntu1
Architecture: i386
Date: Fri Mar 2 18:57:09 2012
ExecutablePath: /usr/bin/htop
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120227)
ProcCmdline: htop
ProcEnviron:
 TERM=xterm
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
Signal: 6
SourcePackage: htop
Stacktrace:
 #0 0x00c8f416 in __kernel_vsyscall ()
 No symbol table info available.
 Cannot access memory at address 0xbff5dcc0
StacktraceTop:

ThreadStacktrace:
 .
 Thread 1 (LWP 3184):
 #0 0x00c8f416 in __kernel_vsyscall ()
 No symbol table info available.
 Cannot access memory at address 0xbff5dcc0
Title: htop crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Thibaut Brandscheid (k1au3-is-37) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x00c8f416 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbff5dcc0
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 1 (LWP 3184):
 #0 0x00c8f416 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbff5dcc0

tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in htop (Ubuntu):
status: New → Confirmed
Revision history for this message
Joshua Powers (powersj) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. In an effort to keep an up-to-date list of bugs to work I have reviewed this report to verify it still requires a fix and it occurs on a supported version of Ubuntu.

I was unable to reproduce your issue in a precise VM with version 1.0.1-1.

It is unfortunate that we were unable to resolve this defect, however there appears to be no further action possible at this time. I am therefore moving the bug to 'Incomplete'. If you disagree or have additional details, please feel free to add a comment and then change the status of the bug to 'Confirmed'.

Changed in htop (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for htop (Ubuntu) because there has been no activity for 60 days.]

Changed in htop (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.