terminator crashed with SIGSEGV in default_3way_compare.part.1.20095()

Bug #1132179 reported by Chris Bainbridge
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
terminator (Fedora)
Won't Fix
Undecided
terminator (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

crash

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: terminator 0.96-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35
Uname: Linux 3.2.0-37-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
Date: Sat Feb 23 17:03:45 2013
ExecutablePath: /usr/share/terminator/terminator
ExecutableTimestamp: 1328095300
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/terminator --sm-config-prefix /terminator-JrxOzi/ --sm-client-id 21fcae7f4-08db-429c-bb9f-cf253093be6b --screen 0
ProcCwd: /home/chrb
SegvAnalysis:
 Segfault happened at: 0x7f0cbd73860a <__strcmp_sse2+26>: movlpd (%rsi),%xmm2
 PC (0x7f0cbd73860a) ok
 source "(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm2" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: terminator
StacktraceTop:
 ?? ()
 PyObject_RichCompare ()
 PyEval_EvalFrameEx ()
 PyEval_EvalCodeEx ()
 ?? ()
Title: terminator crashed with SIGSEGV in PyObject_RichCompare()
UpgradeStatus: Upgraded to precise on 2010-10-30 (846 days ago)
UserGroups: adm admin audio cdrom dialout dip floppy fuse lp lpadmin plugdev root sambashare sudo tty video wireshark

Revision history for this message
In , Kaoru (kaoru-redhat-bugs) wrote :

Description of problem:
Crashed while resizing terminator window

Version-Release number of selected component:
python-2.7.3-13.fc18

Additional info:
backtrace_rating: 4
cmdline: /usr/bin/python /usr/bin/terminator
crash_function: strcmp
executable: /usr/bin/python2.7
kernel: 3.7.4-204.fc18.x86_64
remote_result: NOTFOUND
uid: 1000
var_log_messages: Jan 31 13:58:33 localhost abrt[2741]: Saved core dump of pid 2206 (/usr/bin/python2.7) to /var/spool/abrt/ccpp-2013-01-31-13:58:33-2206 (41684992 bytes)

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 strcmp at ../sysdeps/x86_64/multiarch/strcmp-sse42.S:162
 #1 default_3way_compare at /usr/src/debug/Python-2.7.3/Objects/object.c:789
 #3 try_3way_to_rich_compare at /usr/src/debug/Python-2.7.3/Objects/object.c:907
 #4 do_richcmp at /usr/src/debug/Python-2.7.3/Objects/object.c:930
 #5 PyObject_RichCompare at /usr/src/debug/Python-2.7.3/Objects/object.c:977
 #6 cmp_outcome at /usr/src/debug/Python-2.7.3/Python/ceval.c:4603
 #7 PyEval_EvalFrameEx at /usr/src/debug/Python-2.7.3/Python/ceval.c:2361
 #8 PyEval_EvalCodeEx at /usr/src/debug/Python-2.7.3/Python/ceval.c:3330
 #9 function_call at /usr/src/debug/Python-2.7.3/Objects/funcobject.c:526
 #10 PyObject_Call at /usr/src/debug/Python-2.7.3/Objects/abstract.c:2529

Potential duplicate: bug 847483

Revision history for this message
Chris Bainbridge (chris-bainbridge) wrote :
Revision history for this message
In , Jens (jens-redhat-bugs) wrote :

I had the same crash whilst re-sizing terminator window.

Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 default_3way_compare.part.1.20095 ()
 PyObject_RichCompare ()
 PyEval_EvalFrameEx ()
 PyEval_EvalCodeEx ()
 function_call ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in terminator (Ubuntu):
importance: Undecided → Medium
summary: - terminator crashed with SIGSEGV in PyObject_RichCompare()
+ terminator crashed with SIGSEGV in default_3way_compare.part.1.20095()
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in terminator (Ubuntu):
status: New → Confirmed
Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Changed in terminator (Fedora):
importance: Unknown → Undecided
status: Unknown → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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