oneconf-service crashed with SIGSEGV in debListParser::LoadReleaseInfo()

Bug #857386 reported by Callum Williams
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
oneconf (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I had just opened up the software center and oneconf crashed.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: oneconf 0.2.6.6
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Fri Sep 23 14:14:13 2011
ExecutablePath: /usr/share/oneconf/oneconf-service
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/oneconf/oneconf-service
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f53907c5686 <_ZN13debListParser15LoadReleaseInfoERN8pkgCache15PkgFileIteratorER6FileFdSs+630>: mov %eax,(%r15)
 PC (0x7f53907c5686) ok
 source "%eax" ok
 destination "(%r15)" (0x7f538adfe0a4) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: oneconf
StacktraceTop:
 debListParser::LoadReleaseInfo(pkgCache::PkgFileIterator&, FileFd&, std::string) () from /usr/lib/libapt-pkg.so.4.11
 debPackagesIndex::Merge(pkgCacheGenerator&, OpProgress*) const () from /usr/lib/libapt-pkg.so.4.11
 ?? () from /usr/lib/libapt-pkg.so.4.11
 pkgCacheGenerator::MakeStatusCache(pkgSourceList&, OpProgress*, MMap**, bool) () from /usr/lib/libapt-pkg.so.4.11
 pkgCacheFile::BuildCaches(OpProgress*, bool) () from /usr/lib/libapt-pkg.so.4.11
Title: oneconf-service crashed with SIGSEGV in debListParser::LoadReleaseInfo()
UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Callum Williams (thegooball) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 debListParser::LoadReleaseInfo (this=0x7fff1d267090, FileI=..., File=<optimized out>, component=<optimized out>) at deb/deblistparser.cc:860
 debPackagesIndex::Merge (this=0x29dc620, Gen=<optimized out>, Prog=<optimized out>) at deb/debindexfile.cc:342
 BuildCache (Gen=..., Progress=0x7fff1d2681d0, CurrentSize=@0x7fff1d2680f0, TotalSize=83049869, Start=..., End=...) at pkgcachegen.cc:1067
 pkgCacheGenerator::MakeStatusCache (List=<optimized out>, Progress=0x7fff1d2681d0, OutMap=0x2fcb460, AllowMem=32) at pkgcachegen.cc:1261
 pkgCacheFile::BuildCaches (this=0x2fcb450, Progress=0x7fff1d2681d0, WithLock=<optimized out>) at cachefile.cc:80

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in oneconf (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in oneconf (Ubuntu):
status: New → Confirmed
Revision history for this message
Robert Roth (evfool) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #854090, so it 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. Feel free to continue to report any other bugs you may find.

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.