aptd crashed with SIGSEGV in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::compare().

Bug #812994 reported by gogo
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-apt (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

aptd crashed with SIGSEGV in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::compare().

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: aptdaemon 0.43+bzr662-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7
Uname: Linux 3.0.0-5-generic x86_64
Architecture: amd64
Date: Tue Jul 19 18:23:17 2011
ExecutablePath: /usr/sbin/aptd
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110716)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/aptd
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7fc815eb3601: pcmpeqb (%rax),%xmm0
 PC (0x7fc815eb3601) ok
 source "(%rax)" (0x7fc80aaf25f0) not located in a known VMA region (needed readable region)!
 destination "%xmm0" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: aptdaemon
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 std::basic_string<char, std::char_traits<char>, std::allocator<char> >::compare(char const*) const () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 pkgCacheGenerator::FinishCache(OpProgress*) () from /usr/lib/libapt-pkg.so.4.10
 pkgCacheGenerator::MakeStatusCache(pkgSourceList&, OpProgress*, MMap**, bool) () from /usr/lib/libapt-pkg.so.4.10
 pkgCacheFile::BuildCaches(OpProgress*, bool) () from /usr/lib/libapt-pkg.so.4.10
Title: aptd crashed with SIGSEGV in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::compare()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
gogo (trebelnik-stefina) wrote :
visibility: private → public
tags: removed: need-amd64-retrace
Changed in aptdaemon (Ubuntu):
status: New → Confirmed
affects: aptdaemon (Ubuntu) → python-apt (Ubuntu)
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.