update-apt-xapian-index crashed with SIGSEGV in PyObject_GetAttr()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apt-xapian-index (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Crash during regular apt-get upgrade.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: apt-xapian-index 0.45ubuntu4
ProcVersionSign
Uname: Linux 3.13.0-16-generic x86_64
NonfreeKernelMo
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CrashCounter: 1
Date: Fri Mar 7 09:47:28 2014
ExecutablePath: /usr/sbin/
InstallationDate: Installed on 2014-02-01 (33 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140201)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/sbin/
ProcEnviron:
LANGUAGE=en_GB:en
TERM=linux
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/sh
SegvAnalysis:
Segfault happened at: 0x7fe7b6798d5e: mov (%rax),%eax
PC (0x7fe7b6798d5e) ok
source "(%rax)" (0x7fec61efa4e0) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: apt-xapian-index
StacktraceTop:
?? () from /usr/lib/
?? ()
PyObject_GetAttr ()
PyEval_EvalFrameEx ()
?? ()
Title: update-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1220013, so 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. Please continue to report any other bugs you may find.