warzone2100 crashed with SIGSEGV in memcpy()

Bug #182171 reported by Jaakan Shorter
10
Affects Status Importance Assigned to Milestone
warzone2100 (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: warzone2100

I hosted a game with my Desktop (AMD64) as host and laptop (2x AMD64).
the game got out of sync and locked up at the and of the game.

I had to hit ctrl+alt+backspace to get out of it

ProblemType: Crash
Architecture: amd64
Date: Fri Jan 11 19:04:41 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/games/warzone2100
NonfreeKernelModules: fglrx
Package: warzone2100 2.1.0~0.svn3330-1
PackageArchitecture: amd64
ProcCmdline: warzone2100 --resolution 1280x800
ProcCwd: /home/jaakan
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: warzone2100
StacktraceTop:
 memcpy () from /lib/libc.so.6
 ?? () from /usr/lib/libSDL-1.2.so.0
 ?? () from /usr/lib/libSDL-1.2.so.0
 SDL_SetCursor () from /usr/lib/libSDL-1.2.so.0
 SDL_FreeCursor () from /usr/lib/libSDL-1.2.so.0
Title: warzone2100 crashed with SIGSEGV in memcpy()
Uname: Linux jms1000 2.6.24-3-generic #1 SMP Thu Jan 3 22:50:33 UTC 2008 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev sambashare scanner video

Tags: apport-crash
Revision history for this message
Jaakan Shorter (jaakanshorter) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:memcpy () from /lib/libc.so.6
SDL_DrawCursorNoLock (screen=0x11c1a40) at ../../src/video/SDL_cursor.c:624
SDL_DrawCursor (screen=0x11c1a40) at ../../src/video/SDL_cursor.c:652
SDL_SetCursor (cursor=0x11c4060) at ../../src/video/SDL_cursor.c:217
SDL_FreeCursor (cursor=0x11be6d0) at ../../src/video/SDL_cursor.c:243

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in warzone2100:
importance: Undecided → Medium
Revision history for this message
Caroline Ford (secretlondon) wrote :
Changed in warzone2100:
status: New → Confirmed
Revision history for this message
Caroline Ford (secretlondon) wrote :

Upstream rejected.

Per I. Mathisen
Update of bug #11043 (project warzone):

                 Status: None => Invalid
            Assigned to: None => per
            Open/Closed: Open => Closed

   _______________________________________________________

Follow-up Comment #1:

Network code from this revision is known to be bad. However, this looks like
a graphics driver bug more than anything else. In either case, nothing more
to go on for us here.

Revision history for this message
Dara Adib (daradib) wrote :

This bug has been fixed for the most part in Intrepid, which is running warzone 2.1.0~1.beta4-2. According to upstream:

"[In Warzone 2.1 beta 4] The multi player code has been improved <emphasis>severely</emphasis> since beta 2, but running out of sync is still possible. Though it barely happens anymore, and the differences tend to be significantly smaller."

Note: The bug reporter was running warzone2100 2.1.0~0.svn3330-1, which is even before beta 2 was released.

The only solution for Ubuntu 8.04 and previous versions is to backport warzone 2.1.0~1.beta4-2 or later versions in the future. If you wish to file a backport request, please follow these instructions: https://help.ubuntu.com/community/UbuntuBackports#How%20to%20request%20new%20packages

Changed in warzone2100:
status: Confirmed → Fix Released
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.