aptd crashed with SIGSEGV in debListParser::LoadReleaseInfo()

Bug #861856 reported by Mauricio Pretto on 2011-09-28
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apt (Ubuntu)
Medium
Unassigned

Bug Description

..

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: aptdaemon 0.43+bzr697-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: wl fglrx
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Mon Sep 26 13:47:38 2011
DesktopFile: /usr/share/aptdaemon/aptdaemon.desktop
ExecutablePath: /usr/sbin/aptd
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64+mac (20110919)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/aptd
ProcCwd: /
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7f5f79c44686 <_ZN13debListParser15LoadReleaseInfoERN8pkgCache15PkgFileIteratorER6FileFdSs+630>: rex
 PC (0x7f5f79c44686) ok
 SP (0x7fff5adedb50) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: aptdaemon
StacktraceTop:
 debListParser::LoadReleaseInfo(pkgCache::PkgFileIterator&, FileFd&, std::string) () from /usr/lib/libapt-pkg.so.4.11
 debTranslationsIndex::Exists() const () from /usr/lib/libapt-pkg.so.4.11
 ?? ()
 ?? ()
 ?? ()
Title: aptd crashed with SIGSEGV in debListParser::LoadReleaseInfo()
UpgradeStatus: Upgraded to oneiric on 2011-09-26 (2 days ago)
UserGroups:

Mauricio Pretto (pretto) wrote :

StacktraceTop:
 _M_data (this=0x7fff5adedb90) at /usr/include/c++/4.6/bits/basic_string.h:288
 _M_rep (this=0x7fff5adedb90) at /usr/include/c++/4.6/bits/basic_string.h:296
 length (this=0x7fff5adedb90) at /usr/include/c++/4.6/bits/basic_string.h:717
 WriteUniqString (S=..., this=0x14) at ../build/include/apt-pkg/pkgcachegen.h:85
 WriteUniqString (S=..., this=<optimized out>) at ../build/include/apt-pkg/pkgcachegen.h:125

Changed in aptdaemon (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

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

Changed in aptdaemon (Ubuntu):
status: New → Confirmed
visibility: private → public
affects: aptdaemon (Ubuntu) → apt (Ubuntu)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers