python2.6 crashed with SIGSEGV in PyThreadState_New()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gnome-orca |
Invalid
|
Undecided
|
Unassigned | ||
| pyorbit (Ubuntu) |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
Binary package hint: python2.6
This happened while I was testing orca on Lucid i386
ProblemType: Crash
Architecture: i386
Date: Tue Mar 23 20:22:06 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/python2.6
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
Package: python2.6-minimal 2.6.5-1ubuntu2
ProcCmdline: /usr/bin/python -c import\ orca.orca;\ orca.orca.main()
ProcEnviron:
PATH=(cusUser Name, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x80fdbb5 <PyThreadState_
PC (0x080fdbb5) ok
source "0x4(%esi)" (0x00000004) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: python2.6
StacktraceTop:
PyThreadState_New ()
PyGILState_Ensure ()
?? () from /usr/lib/
?? () from /usr/lib/
ORBit_
Title: python2.6 crashed with SIGSEGV in PyThreadState_New()
Uname: Linux 2.6.32-16-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev nopasswdlogin plugdev sambashare tape video
| affects: | python2.6 (Ubuntu) → pyorbit (Ubuntu) |
| visibility: | private → public |

segfault at 4 ip 080fdbb5 sp bf9318f0 error 4 in python2. 6[8048000+ 1e0000]