aptitude crashed with SIGSEGV in pkgAcquire::Worker::RunMessages()

Bug #525171 reported by danrgmc
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
aptitude (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: aptitude

10.04 LTS
0.4.11.11-1ubuntu9
package crashed but continued working anyway
I'm running this as a virtual machine with sun virtualbox

ProblemType: Crash
Architecture: i386
Date: Sat Feb 20 22:34:07 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/aptitude
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100113)
Package: aptitude 0.4.11.11-1ubuntu9
ProcAttrCurrent: unconfined (enforce)
ProcCmdline: aptitude update
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
SegvAnalysis:
 Segfault happened at: 0x81875d7: mov 0x4(%eax),%edx
 PC (0x081875d7) ok
 source "0x4(%eax)" (0x20202024) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: aptitude
StacktraceTop:
 ?? ()
 pkgAcquire::Worker::RunMessages() ()
 pkgAcquire::Worker::InFdReady() ()
 pkgAcquire::RunFds(fd_set*, fd_set*) ()
 pkgAcquire::Run(int) ()
Title: aptitude crashed with SIGSEGV in pkgAcquire::Worker::RunMessages()
Uname: Linux 2.6.32-14-generic i686
UserGroups:

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #525073, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-i386-retrace
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.