aptitude crashed with SIGSEGV in pkgRecords::Lookup()

Bug #181406 reported by Dagfinn Ilmari Mannsåker
124
Affects Status Importance Assigned to Milestone
aptitude
Fix Released
Unknown
aptitude (Ubuntu)
Fix Released
Critical
Unassigned

Bug Description

Binary package hint: aptitude

The crash occurred when hitting 'U' in at the main package listing with no actions pending and the extended description area hidden.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Wed Jan 9 02:38:13 2008
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:
 pkgRecords::Lookup () from /usr/lib/libapt-pkg-libc6.7-6.so.4.6
 pkg_description_widget::set_package (this=0x82d54f8, pkg=@0x82d6838,
 info_area_multiplex::set_package (this=0x82d6788, pkg=@0x82d6838, ver=@0x82d6844)
 info_area_multiplex::reset_package (this=0x82d6788) at pkg_view.cc:447
 do_mark_upgradable () at /usr/include/sigc++-2.0/sigc++/signal.h:550
Title: aptitude crashed with SIGSEGV in pkgRecords::Lookup()
Uname: Linux vesla 2.6.24-2-generic #1 SMP Thu Dec 20 17:36:12 GMT 2007 i686 GNU/Linux
UserGroups:

Tags: apport-crash
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:pkgRecords::Lookup (this=0x8540db0, Ver=@0xbfa9bef0) at pkgrecords.cc:60
pkg_description_widget::set_package (this=0x82d54f8, pkg=@0x82d6838, ver=@0x82d6844)
info_area_multiplex::set_package (this=0x82d6788, pkg=@0x82d6838, ver=@0x82d6844)
info_area_multiplex::reset_package (this=0x82d6788) at pkg_view.cc:447
do_mark_upgradable () at /usr/include/sigc++-2.0/sigc++/signal.h:550

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
Changed in aptitude:
importance: Undecided → Medium
Revision history for this message
Rolf Leggewie (r0lf) wrote :

dupe of bug 176450? both fail in pkgRecord::Lookup(), but the way to trigger them was different, so it might be two different animals.

Changed in aptitude:
status: New → Confirmed
importance: Medium → High
Revision history for this message
Kjell Braden (afflux) wrote :

Forwarded to upstream (debian).

Changed in aptitude:
status: Unknown → New
Revision history for this message
Jacob (jleems86) wrote :

For me, the crash happened when i selected a package and hit "P" to mark it to be purged

Revision history for this message
Rolf Leggewie (r0lf) wrote :

upstream cannot reproduce the problem in the most recent version of aptitude. Maybe time for an update?

Revision history for this message
John Pyper (jpyper) wrote : Re: [Bug 181406] Re: aptitude crashed with SIGSEGV in pkgRecords::Lookup()

Rolf,

Thank you for your reply. I have been noticing this issue after having
my system running for 3+ days. I have an alias set for easy updates
for me:

alias osupgrade="sudo aptitude update && sudo aptitude safe-upgrade"

I run the osupgrade alias at least once a day to make sure my hardy
installation is up to date.

-John

On 4/18/08, Rolf Leggewie <email address hidden> wrote:
> upstream cannot reproduce the problem in the most recent version of
> aptitude. Maybe time for an update?
>
> --
> aptitude crashed with SIGSEGV in pkgRecords::Lookup()
> https://bugs.launchpad.net/bugs/181406
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Rolf Leggewie (r0lf) wrote :

> I run the osupgrade alias at least once a day to make sure my hardy
> installation is up to date.

hardy is still on 0.4.9 (the same as for the upstream bug report). 0.4.9 is according to the debian report more than a year old and it seems the devs are unwilling to fix in it that version, especially since they cannot reproduce it in the more recent 0.4.10 and 0.4.11

Elevating importance. I believe it would be nice if this was fixed before the hardy release. Not sure if anybody is willing to upload a newer aptitude this close to the release, I guess not. But this will certainly be a highly visible and highly annoying bug.

Changed in aptitude:
importance: High → Critical
Revision history for this message
Rolf Leggewie (r0lf) wrote :

> 0.4.9 is according to the debian report more than a year old

well, the debian changelog tells a different story, of course. Changes to 0.4.9 were still uploaded at the end of last year.

Changed in aptitude:
status: New → Fix Released
Revision history for this message
Thomas Ohms (tohms) wrote :

I need some exercise and so I will have a look on this at weekend. Maybe I can offer a patch for you guys.

Revision history for this message
Thomas Ohms (tohms) wrote : Re: FIXED: aptitude crashed with SIGSEGV in pkgRecords::Lookup()

Bad for me, but I have seen there is already a fixed version 0.4.9-2ubuntu5 in Hardy. So no need to do anything. Please close this Bug!

Revision history for this message
Kjell Braden (afflux) wrote :

Marking fix released as requested.

Changed in aptitude:
status: Confirmed → Fix Released
Revision history for this message
Gianmarco (d-info-q) wrote : Some Answers from abhilash_chandran26

http://belizeandeals.com/zvoaocjn.php?fwdmvaj2tu599

Sent from my iPad
Begin forwarded message:

> The most incomprehensible thing about the world is that it is at all comprehensible.
>
> From: Abhilash_chandran26 -<email address hidden>-
> Date: Tue, 9 Mar 2016 03:58:21 +0000
> To: Ffoundisclosed
> Subject: Some Answers from abhilash_chandran26
>
> http://belizeandeals.com/zvoaocjn.php?fwdmvaj2tu599

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.