Ubuntu
transmageddon package

python3.3 crashed with SIGSEGV in call_function()

Bug #1210860 reported by Leitão on 2013-08-10

10

This bug affects 1 person

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

Bug Description

I don't know...
Sorry !!!

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: python3.3-minimal 3.3.2-3ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-4.13-generic 3.10.1
Uname: Linux 3.10.0-4-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12-0ubuntu3
Architecture: amd64
Date: Sat Aug 10 17:34:38 2013
ExecutablePath: /usr/bin/python3.3
InstallationDate: Installed on 2013-07-15 (26 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130715)
MarkForUpload: True
ProcCmdline: python3 transmageddon.py
SegvAnalysis:
Segfault happened at: 0x58b733 <PyEval_EvalFrameEx+1235>: mov 0x24(%r15),%eax
PC (0x0058b733) ok
source "0x24(%r15)" (0x00000024) 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 ()
PyEval_EvalFrameEx ()
?? ()
?? ()
?? ()
Title: python3.3 crashed with SIGSEGV in PyEval_EvalFrameEx()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

Leitão (piratininga2000) wrote on 2013-08-10:

#1

Dependencies.txt Edit (1.0 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1019 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (317 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (72.9 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (829 bytes, text/plain; charset="utf-8")
Registers.txt Edit (804 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (9.6 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (25.7 KiB, text/plain; charset="utf-8")

Revision history for this message

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

#2

StacktraceTop:
call_function (oparg=<optimized out>, pp_stack=0x7f983fffb480) at ../Python/ceval.c:4067
PyEval_EvalFrameEx (f=f@entry=0x18b3ca0, throwflag=throwflag@entry=0) at ../Python/ceval.c:2679
fast_function (nk=<optimized out>, na=<optimized out>, n=1, pp_stack=0x7f983fffb5d0, func=<optimized out>) at ../Python/ceval.c:4155
call_function (oparg=<optimized out>, pp_stack=0x7f983fffb5d0) at ../Python/ceval.c:4088
PyEval_EvalFrameEx (f=f@entry=0x7f9881847440, throwflag=throwflag@entry=0) at ../Python/ceval.c:2679

Revision history for this message

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

#3

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

Revision history for this message

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

#4

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

Revision history for this message

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

#5

ThreadStacktrace.txt Edit (193.5 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 call_function()
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.