python2.7 crashed with SIGSEGV in pango_start_element()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gtk-vnc (Ubuntu) |
New
|
Medium
|
Unassigned |
Bug Description
suddenly stop
any help
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: python2.7-minimal 2.7.4-2ubuntu3
Uname: Linux 3.10.7-
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: i386
Date: Sun Aug 18 17:40:28 2013
ExecutablePath: /usr/bin/python2.7
InstallationDate: Installed on 2013-01-15 (215 days ago)
InstallationMedia: This
MarkForUpload: True
ProcCmdline: python window.py
ProcEnviron:
TERM=linux
PATH=(custom, no user)
SegvAnalysis:
Segfault happened at: 0xb6df5f60: mov %ebp,0x4
PC (0xb6df5f60) ok
source "%ebp" ok
destination "0x4" (0x00000004) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: python2.7
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /lib/i386-
g_markup_
?? () from /usr/lib/
Title: python2.7 crashed with SIGSEGV in g_markup_
UpgradeStatus: Upgraded to raring on 2013-08-18 (0 days ago)
UserGroups:
affects: | python2.7 (Ubuntu) → gtk-vnc (Ubuntu) |
information type: | Private → Public |