balazar crashed with SIGSEGV in PyEval_EvalFrameEx()

Bug #509184 reported by Klaus Doblmann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
balazar (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: balazar

the game crashed when starting a new game

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Mon Jan 18 16:22:03 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/games/balazar
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100113)
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: wl
Package: balazar 0.3.4.ds1-6
PackageArchitecture: all
ProcCmdline: /usr/bin/python -O /usr/games/balazar
ProcEnviron:
 LANG=de_AT.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
SegvAnalysis:
 Segfault happened at: 0x7fc874010372: movl $0xffffffff,0x158(%rax)
 PC (0x7fc874010372) ok
 source "$0xffffffff" ok
 destination "0x158(%rax)" (0x431b0158) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: balazar
StacktraceTop:
 ?? ()
 PyEval_EvalFrameEx ()
 PyEval_EvalCodeEx ()
 PyEval_EvalFrameEx ()
 PyEval_EvalFrameEx ()
Tags: lucid
Title: balazar crashed with SIGSEGV in PyEval_EvalFrameEx()
Uname: Linux 2.6.32-10-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Klaus Doblmann (moviemaniac) wrote :
Revision history for this message
dino99 (9d9) wrote :
Changed in balazar (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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