aptitude crashed with SIGSEGV when forgetting new packages

Bug #177850 reported by Dagfinn Ilmari Mannsåker
24
This bug affects 2 people
Affects Status Importance Assigned to Milestone
aptitude (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: aptitude

At the main aptitude screen I hit "f" to forget which packages were new, and aptitude crashed.

ProblemType: Crash
Architecture: i386
Date: Fri Dec 21 08:27:45 2007
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/aptitude
Package: aptitude 0.4.9-2ubuntu3
PackageArchitecture: i386
ProcCmdline: aptitude -u
ProcCwd: /home/ilmari
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
 LC_TIME=en_IE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: aptitude
StacktraceTop: ?? ()
Title: aptitude crashed with SIGSEGV
Uname: Linux vesla 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux
UserGroups:

SegvAnalysis:
 Segfault happened at: 0x80fb4a4 <_ZN22pkg_description_widget11set_packageERKN8pkgCache11PkgIteratorERKNS0_11VerIteratorE+100>: mov %esp,%eax
 PC (0x080fb4a4) ok
 source "%esp" ok
 destination "%eax" ok
 SP (0xbfdd59f0) ok
 Reason could not be automatically determined.
SegvReason: Reason could not be automatically determined.

Revision history for this message
Dagfinn Ilmari Mannsåker (ilmari) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? () from /lib/ld-linux.so.2
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Revision history for this message
Bruce Cowan (bruce89-deactivatedaccount) wrote :

I can confirm this.

Changed in aptitude:
status: New → Confirmed
Revision history for this message
Matteo Settenvini (tchernobog) wrote :

Seconding. Unfortunately the stacktrace doesn't say much as it is; so I did a session and generated a full backtrace. This is the result, but I don't know if it's enough. If it isn't, please tell me and I'll try and get something better -- maybe setting a breakpoint on do_forget_new ().

Revision history for this message
brentpieczynski (brentpieczynski) wrote :

After a fix release for Firefox was installed, I finished reporting a bug for it. This act of having reporting a bug which was caused by patching another bug, does seem to be the cause of this present-bug.

Kees Cook (kees)
description: updated
Kees Cook (kees)
description: updated
Rolf Leggewie (r0lf)
tags: added: hardy
Revision history for this message
dino99 (9d9) wrote :

That version has died long ago; no more supported

Changed in aptitude (Ubuntu):
status: Confirmed → Invalid
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.