gedit crashed with SIGSEGV in PyEval_EvalFrameEx()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gedit (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Happened during editing but I don't exactly remember what I pressed right before it happened. The changes since the last save are gone.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gedit 3.2.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Mon Oct 3 22:39:52 2011
ExecutablePath: /usr/bin/gedit
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64+mac (20110427.1)
ProcCmdline: gedit src/annotate.coffee
SegvAnalysis:
Segfault happened at: 0x7f17e1a5ba10: mov -0x8(%rsi),%rdx
PC (0x7f17e1a5ba10) ok
source "-0x8(%rsi)" (0x0000007c) not located in a known VMA region (needed readable region)!
destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gedit
StacktraceTop:
?? () from /lib/x86_
?? () from /usr/lib/
?? () from /usr/lib/
PyEval_EvalFrameEx () from /usr/lib/
PyEval_EvalCodeEx () from /usr/lib/
Title: gedit crashed with SIGSEGV in PyEval_
UpgradeStatus: Upgraded to oneiric on 2011-09-30 (3 days ago)
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #863773, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.