update-apt-xapian-index crashed with SIGSEGV in getset_get.11217()

Bug #1272241 reported by Iain Lane
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apt-xapian-index (Ubuntu)
New
Undecided
Unassigned

Bug Description

I see this crash pop up from time-to-time. I guess it's from the cron job.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: apt-xapian-index 0.45ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
Uname: Linux 3.13.0-5-generic x86_64
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Fri Jan 24 09:32:48 2014
ExecutablePath: /usr/sbin/update-apt-xapian-index
InstallationDate: Installed on 2012-10-07 (473 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/update-apt-xapian-index -q -u
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=linux
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/sh
SegvAnalysis:
 Segfault happened at: 0x7fe66ed72d5e: mov (%rax),%eax
 PC (0x7fe66ed72d5e) ok
 source "(%rax)" (0x7feb17ad5480) 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/python2.7/dist-packages/apt_pkg.so
 getset_get.11217 (descr=0x17ff1b8, obj=<apt_pkg.Description at remote 0xb939e10>, type=<optimised out>) at ../Objects/descrobject.c:146
 _PyObject_GenericGetAttrWithDict (dict=0x0, name='file_list', obj=<apt_pkg.Description at remote 0xb939e10>) at ../Objects/object.c:1399
 PyObject_GenericGetAttr (name=<optimised out>, obj=<apt_pkg.Description at remote 0xb939e10>) at ../Objects/object.c:1461
 PyObject_GetAttr (v=<apt_pkg.Description at remote 0xb939e10>, name=<optimised out>) at ../Objects/object.c:1196
SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli'
Title: update-apt-xapian-index crashed with SIGSEGV in getset_get.11217()
UpgradeStatus: Upgraded to trusty on 2013-05-07 (262 days ago)
UserGroups:

Revision history for this message
Iain Lane (laney) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

information type: Private → Public
tags: removed: need-amd64-retrace
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.