Ubuntu

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

Reported by Mahesh Asolkar on 2010-02-21
84
This bug affects 14 people
Affects Status Importance Assigned to Milestone
aptitude (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: aptitude

I ran a routine 'sudo aptitude update && sudo aptitude safe-upgrade' when this crash happened.

Only difference is that I had added a 'karmic' PPA for global menu to see if works in Lucid. I removed the PPA after I made sure global menu package does work. That was the last 'aptitude' related changes I made before the crash.

ProblemType: Crash
Architecture: i386
Date: Sun Feb 21 12:59:10 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
ProcCmdline: aptitude update
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
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:
SegvAnalysis:
 Segfault happened at: 0x818745f: call *%edx
 PC (0x0818745f) ok
 source "*%edx" (0x20202020) not located in a known VMA region (needed readable region)!
 destination "(%esp)" (0xbf943930) ok
SegvReason: reading unknown VMA

Mahesh Asolkar (asolkar) wrote :

StacktraceTop:
 download_signal_log::Fetch (this=0x8b9aa60, item=@0x8be7b88)
 pkgAcquire::Worker::RunMessages (this=0x8be84f0)
 pkgAcquire::Worker::InFdReady (this=0x8be84f0)
 pkgAcquire::RunFds (this=0x8b9d540, RSet=0xbf943bd4,
 pkgAcquire::Run (this=0x8b9d540, PulseIntervall=500000)

Changed in aptitude (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Kees Cook (kees) on 2010-04-22
description: updated
visibility: private → public
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers