py_compile.py crashed with SIGSEGV in freechildren()

Bug #1166296 reported by Jeremiah Njoroge
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
python2.7 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

updating the system via apt-get update/dist-upgrade when the crash occurred.

Observed the following message in the terminal console

Errors were encountered while processing:
 python2.7
 python
 libpython2.7-dbg:amd64
 python2.7-dbg
 libpython-dbg:amd64
 python-dbg
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: libpython2.7-minimal 2.7.4-1ubuntu1
Uname: Linux 3.9.0-030900rc5-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Mon Apr 8 09:11:56 2013
ExecutablePath: /usr/lib/python2.7/py_compile.py
InstallationDate: Installed on 2013-03-19 (19 days ago)
InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Alpha amd64 (20130319)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x4d7ac8 <freechildren+152>: mov 0x18(%r12),%r11d
 PC (0x004d7ac8) ok
 source "0x18(%r12)" (0x22ca18b675) not located in a known VMA region (needed readable region)!
 destination "%r11d" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: python2.7
StacktraceTop:
 freechildren (n=0x22ca18b65d) at ../Parser/node.c:143
 freechildren (n=0x7f086b73b390) at ../Parser/node.c:144
 freechildren (n=0x2416690) at ../Parser/node.c:144
 freechildren (n=0x7f086b7352d8) at ../Parser/node.c:144
 freechildren (n=0x7f086b7521e8) at ../Parser/node.c:144
Title: py_compile.py crashed with SIGSEGV in freechildren()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Jeremiah Njoroge (jnjoroge) wrote :
information type: Private → Public
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in python2.7 (Ubuntu):
status: New → Confirmed
Revision history for this message
Matthias Klose (doko) wrote :

closing, only seen on Ubuntu 13.04 apparently

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