Ubuntu
terminator package

terminator crashed with SIGSEGV in PyType_IsSubtype()

Bug #1155734 reported by Iain Lane on 2013-03-15

10

This bug affects 1 person

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

Bug Description

I used Unity's "Show Desktop" icon from alt-tab.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: terminator 0.96-2fakesync1
ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2
Uname: Linux 3.8.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
Date: Fri Mar 15 15:59:39 2013
ExecutablePath: /usr/share/terminator/terminator
InstallationDate: Installed on 2012-10-07 (158 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/terminator
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, user)
XDG_RUNTIME_DIR=<set>
LANG=en_GB.UTF-8
SHELL=/bin/zsh
SegvAnalysis:
Segfault happened at: 0x4d6a20: mov 0x10(%rcx),%r8
PC (0x004d6a20) ok
source "0x10(%rcx)" (0x7369207320202030) not located in a known VMA region (needed readable region)!
destination "%r8" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: terminator
StacktraceTop:
?? ()
PyObject_RichCompare ()
PyEval_EvalFrameEx ()
PyEval_EvalFrameEx ()
PyEval_EvalCodeEx ()
Title: terminator crashed with SIGSEGV in PyObject_RichCompare()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo vboxusers

Tags:

Revision history for this message

Iain Lane (laney) wrote on 2013-03-15:

#1

Dependencies.txt Edit (10.0 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (502 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (78.4 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (846 bytes, text/plain; charset="utf-8")
Registers.txt Edit (712 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (5.6 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (9.5 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2013-03-15:

#2

StacktraceTop:
PyType_IsSubtype (b=0x866a80 <PyBool_Type>, a=0x16f2b18) at ../Objects/typeobject.c:1155
try_rich_compare.20464 (v=0x873d50 <_Py_ZeroStruct>, w=0x873d30 <_Py_TrueStruct>, op=2) at ../Objects/object.c:614
do_richcmp (op=2, w=0x873d30 <_Py_TrueStruct>, v=0x873d50 <_Py_ZeroStruct>) at ../Objects/object.c:930
PyObject_RichCompare (v=0x873d50 <_Py_ZeroStruct>, w=w@entry=0x873d30 <_Py_TrueStruct>, op=2) at ../Objects/object.c:982
cmp_outcome (w=0x873d30 <_Py_TrueStruct>, v=<optimized out>, op=<optimized out>) at ../Python/ceval.c:4526

Revision history for this message

Apport retracing service (apport) wrote on 2013-03-15: Stacktrace.txt

#3

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

Revision history for this message

Apport retracing service (apport) wrote on 2013-03-15: StacktraceSource.txt

#4

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

Revision history for this message

Apport retracing service (apport) wrote on 2013-03-15: ThreadStacktrace.txt

#5

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

Changed in terminator (Ubuntu):
importance:	Undecided → Medium
summary:	- terminator crashed with SIGSEGV in PyObject_RichCompare() + terminator crashed with SIGSEGV in PyType_IsSubtype()
tags:	removed: need-amd64-retrace

Iain Lane (laney) on 2013-03-18

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.