update-apt-xapian-index crashed with SIGSEGV in pkgCacheGenerator::MakeStatusCache()

Bug #654154 reported by rd12686950 on 2010-10-03
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apt-xapian-index (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: apt-xapian-index

I am opening the system

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: apt-xapian-index 0.39ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
CrashCounter: 1
Date: Sat Oct 2 11:51:14 2010
ExecutablePath: /usr/sbin/update-apt-xapian-index
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/update-apt-xapian-index --update -q
ProcEnviron:
 PATH=(custom, no user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x1a5fb6: rep movsl %ds:(%esi),%es:(%edi)
 PC (0x001a5fb6) ok
 source "%ds:(%esi)" (0xbfcefe2b) ok
 destination "%es:(%edi)" (0x0000007b) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: apt-xapian-index
StacktraceTop:
 ?? () from /lib/libc.so.6
 ?? ()
 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
 pkgCacheFile::Open(OpProgress*, bool) () from /usr/lib/libapt-pkg.so.4.10
Title: update-apt-xapian-index crashed with SIGSEGV in pkgCacheGenerator::MakeStatusCache()
UserGroups:

rd12686950 (rd12686950) wrote :

StacktraceTop:
 __memcpy_ia32 () from /lib/libc.so.6
 ?? ()
 pkgCacheGenerator::MakeStatusCache (List=@0x917f350,
 pkgCacheFile::BuildCaches (this=0x917a530,
 pkgCacheFile::Open (this=0x917a530, Progress=0xbfcf4298,

Changed in apt-xapian-index (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Steve Beattie (sbeattie) on 2015-04-06
information type: Private → Public
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers