Ubuntu
transmageddon package

python3.3 crashed with SIGSEGV in tupledealloc.5509()

Bug #1215611 reported by Javier Peces on 2013-08-22

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	transmageddon (Ubuntu)	New	Medium	Unassigned

Bug Description

Running transmageddon

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: python3.3-minimal 3.3.2-3ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-3.7-generic 3.11.0-rc6
Uname: Linux 3.11.0-3-generic x86_64
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Thu Aug 22 22:09:53 2013
ExecutablePath: /usr/bin/python3.3
InstallationDate: Installed on 2013-08-11 (10 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130811)
MarkForUpload: True
ProcCmdline: python3 transmageddon.py
SegvAnalysis:
Segfault happened at: 0x57a1d6: mov 0x98(%r13),%eax
PC (0x0057a1d6) ok
source "0x98(%r13)" (0x00000098) not located in a known VMA region (needed readable region)!
destination "%eax" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: python3.3
StacktraceTop:
?? ()
PyEval_EvalFrameEx ()
?? ()
?? ()
PyObject_CallObject ()
Title: python3.3 crashed with SIGSEGV in PyEval_EvalFrameEx()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm lpadmin sambashare sudo

Tags:

Revision history for this message

Javier Peces (javierpeces) wrote on 2013-08-22:

#1

Dependencies.txt Edit (1.0 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (503 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (97 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (77.4 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (818 bytes, text/plain; charset="utf-8")
Registers.txt Edit (835 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (5.3 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (31.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2013-08-22:

#2

StacktraceTop:
tupledealloc.5509 (op=0x7f46bfcf7c68) at ../Objects/tupleobject.c:232
call_function (oparg=<optimized out>, pp_stack=0x7f4699db14d0) at ../Python/ceval.c:4069
PyEval_EvalFrameEx (f=f@entry=0x7f4690026d00, throwflag=throwflag@entry=0) at ../Python/ceval.c:2679
PyEval_EvalCodeEx (closure=<optimized out>, kwdefs=<optimized out>, defcount=<optimized out>, defs=0x0, kwcount=<optimized out>, kws=<optimized out>, argcount=<optimized out>, args=<optimized out>, locals=0x0, globals=<optimized out>, _co=0x7f46cce6c9c0) at ../Python/ceval.c:3437
function_call.70414 (func=func@entry=0x7f46ccccbcb0, arg=arg@entry=0x7f46cedcb190, kw=kw@entry=0x0) at ../Objects/funcobject.c:633

Revision history for this message

Apport retracing service (apport) wrote on 2013-08-22: Stacktrace.txt

#3

Stacktrace.txt Edit (13.7 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2013-08-22: StacktraceSource.txt

#4

StacktraceSource.txt Edit (2.6 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2013-08-22: ThreadStacktrace.txt

#5

ThreadStacktrace.txt Edit (55.7 KiB, text/plain)

Changed in python3.3 (Ubuntu):
importance:	Undecided → Medium
summary:	- python3.3 crashed with SIGSEGV in PyEval_EvalFrameEx() + python3.3 crashed with SIGSEGV in tupledealloc.5509()
tags:	removed: need-amd64-retrace

Matthias Klose (doko) on 2013-09-18

affects:	python3.3 (Ubuntu) → transmageddon (Ubuntu)
information type:	Private → Public

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.