python2.7 crashed with SIGSEGV in PyObject_Free()

Bug #854132 reported by Corbin
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python2.7 (Ubuntu)
Expired
Medium
Unassigned

Bug Description

python2.7 crashed after a failed update. Apport poped up, so I am reporting. If you need more info, just tell me what.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: python2.7-minimal 2.7.2-5
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
Date: Mon Sep 19 11:50:16 2011
ExecutablePath: /usr/bin/python2.7
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: /usr/bin/python2.7 -m py_compile -
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x80a9884 <PyObject_Free+20>: mov 0x10(%eax),%ecx
 PC (0x080a9884) ok
 source "0x10(%eax)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: python2.7
StacktraceTop:
 PyObject_Free ()
 ?? ()
 ?? ()
 ?? ()
 PyNode_Free ()
Title: python2.7 crashed with SIGSEGV in PyObject_Free()
UpgradeStatus: Upgraded to oneiric on 2011-09-09 (10 days ago)
UserGroups:

Revision history for this message
Corbin (corbin) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 PyObject_Free (p=0x80) at ../Objects/obmalloc.c:969
 freechildren (n=<optimized out>) at ../Parser/node.c:137
 freechildren (n=0xb74cc920) at ../Parser/node.c:133
 freechildren (n=0xb74cc908) at ../Parser/node.c:133
 freechildren (n=0xb74cc8f0) at ../Parser/node.c:133

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 python2.7 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Matthias Klose (doko) wrote :

is this reproducible?

visibility: private → public
Changed in python2.7 (Ubuntu):
status: New → Incomplete
Revision history for this message
Corbin (corbin) wrote :

Probably not. I did have it occur multiple different times, but I couldn't see any relation between them, and never tried to reproduce it. Unfortunately, I have since downgraded to Natty, so I cannot provide any further assistance.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for python2.7 (Ubuntu) because there has been no activity for 60 days.]

Changed in python2.7 (Ubuntu):
status: Incomplete → Expired
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.