[Pkg-games-ubuntu] [Bug 551335] Re: warzone2100 crashed with SIGSEGV in checkDroid()

[Paul Wise (Debian)]

Unfortunately the stack dump doesn't contain any debug symbols so this
bug report is not particularly useful. Please check your apport setup,
it may not be sending crash dumps properly. You can test crashes by
running warzone2100 --crash on the command-line.

** Changed in: warzone2100 (Ubuntu)
       Status: New => Incomplete

-- 
warzone2100 crashed with SIGSEGV in checkDroid()
https://bugs.launchpad.net/bugs/551335
You received this bug notification because you are a member of
Debian/Ubuntu Games Team, which is subscribed to warzone2100 in ubuntu.

Status in “warzone2100” package in Ubuntu: Incomplete

Bug description:
Binary package hint: warzone2100

First map of first campaign, started an attack on units to the east when the game crashed.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: warzone2100 2.2.4-3
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-17-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Tue Mar 30 01:22:45 2010
ExecutablePath: /usr/games/warzone2100
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
ProcCmdline: warzone2100
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x80e5044 <checkDroid+148>:	cmpl   $0xf,0x8(%eax)
 PC (0x080e5044) ok
 source "$0xf" ok
 destination "0x8(%eax)" (0x0000000a) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: warzone2100
StacktraceTop:
 checkDroid ()
 checkObject ()
 actionInsideMinRange ()
 orderDroidBase ()
 orderDroidObj ()
Title: warzone2100 crashed with SIGSEGV in checkDroid()
UserGroups: adm admin cdrom dialout dip fax floppy fuse plugdev root tape vboxusers video