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

Bug #654427 reported by Michael Booth
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apt-xapian-index (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: apt-xapian-index

Ubuntu 10.10

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
NonfreeKernelModules: nvidia
Architecture: i386
Date: Mon Oct 4 07:48:20 2010
Disassembly: => 0x20: Cannot access memory at address 0x20
ExecutablePath: /usr/sbin/update-apt-xapian-index
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/update-apt-xapian-index -q
ProcEnviron:
 PATH=(custom, no user)
 SHELL=/bin/sh
SegvAnalysis:
 Segfault happened at: 0x20: Cannot access memory at address 0x20
 PC (0x00000020) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: apt-xapian-index
StacktraceTop:
 ?? ()
 ?? ()
 PyGC_Collect ()
 Py_Finalize ()
 ?? ()
Title: update-apt-xapian-index crashed with SIGSEGV in PyGC_Collect()
UserGroups:

Revision history for this message
Michael Booth (boothmichaelj) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 PyGC_Collect () at ../Modules/gcmodule.c:1292
 Py_Finalize () at ../Python/pythonrun.c:434
 handle_system_exit () at ../Python/pythonrun.c:1758
 PyErr_PrintEx (set_sys_last_vars=<value optimized out>)

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 apt-xapian-index (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Steve Beattie (sbeattie)
information type: Private → Public
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.