update-apt-xapian-index crashed with SIGSEGV in PyEval_EvalFrameEx()

Bug #655412 reported by David lambert on 2010-10-05
This bug affects 2 people
Affects Status Importance Assigned to Milestone
apt-xapian-index (Ubuntu)

Bug Description

Binary package hint: apt-xapian-index

Crash icon just appeared

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: apt-xapian-index 0.39ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic
Uname: Linux 2.6.35-22-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Tue Oct 5 18:02:05 2010
ExecutablePath: /usr/sbin/update-apt-xapian-index
InstallationMedia: Mythbuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/update-apt-xapian-index -q
 PATH=(custom, no user)
 Segfault happened at: 0x808e66b: mov (%eax),%edx
 PC (0x0808e66b) ok
 source "(%eax)" (0x00000100) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: apt-xapian-index
 ?? ()
 PyEval_EvalFrameEx ()
 PyEval_EvalFrameEx ()
 PyEval_EvalFrameEx ()
 ?? ()
Title: update-apt-xapian-index crashed with SIGSEGV in PyEval_EvalFrameEx()

David lambert (dave-lambsys) wrote :

 dictresize (mp=0x98eb4f4, minused=<value optimized out>)
 PyEval_EvalFrameEx (f=0x9c08174, throwflag=0)
 PyEval_EvalFrameEx (f=0x9c074fc, throwflag=0)
 PyEval_EvalFrameEx (f=0x9a1eef4, throwflag=0)
 gen_send_ex (gen=0x9b42f7c, arg=<value optimized out>,

Changed in apt-xapian-index (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Steve Beattie (sbeattie) on 2015-04-04
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