[Bug 854132] Re: python2.7 crashed with SIGSEGV in PyObject_Free()

Launchpad Bug Tracker 854132 at bugs.launchpad.net
Sun Dec 4 04:18:30 UTC 2011

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

** Changed in: python2.7 (Ubuntu)
       Status: Incomplete => Expired

You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to python2.7 in Ubuntu.

  python2.7 crashed with SIGSEGV in PyObject_Free()

Status in “python2.7” package in Ubuntu:

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 -
   PATH=(custom, no user)
   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
   PyObject_Free ()
   ?? ()
   ?? ()
   ?? ()
   PyNode_Free ()
  Title: python2.7 crashed with SIGSEGV in PyObject_Free()
  UpgradeStatus: Upgraded to oneiric on 2011-09-09 (10 days ago)

To manage notifications about this bug go to:

More information about the foundations-bugs mailing list