widelands crashed with SIGSEGV in Widelands::Soldier::battle_update()

Bug #1644838 reported by Guybrush88
This bug report is a duplicate of:  Bug #1636966: Segfault in battle. Edit Remove
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
widelands
New
Critical
Unassigned
widelands (Ubuntu)
New
Medium
Unassigned

Bug Description

I started doing something else while leaving a game running, and I got this crash.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: widelands 1:18-3build3
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Nov 25 14:15:43 2016
ExecutablePath: /usr/games/widelands
InstallationDate: Installed on 2016-10-16 (40 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720)
ProcCmdline: widelands
ProcEnviron:
 LANGUAGE=it_IT
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x6a8e5c <_ZN9Widelands7Soldier13battle_updateERNS_4GameERNS_3Bob5StateE+252>: mov 0x40(%rax),%eax
 PC (0x006a8e5c) ok
 source "0x40(%rax)" (0x00000040) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: widelands
StacktraceTop:
 Widelands::Soldier::battle_update(Widelands::Game&, Widelands::Bob::State&) ()
 Widelands::Bob::act(Widelands::Game&, unsigned int) ()
 Widelands::Cmd_Act::execute(Widelands::Game&) ()
 Widelands::Cmd_Queue::run_queue(int, int&) ()
 Widelands::Game::think() ()
Title: widelands crashed with SIGSEGV in Widelands::Soldier::battle_update()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Guybrush88 (guybrush) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 Widelands::Soldier::battle_update(Widelands::Game&, Widelands::Bob::State&) ()
 Widelands::Bob::act(Widelands::Game&, unsigned int) ()
 Widelands::Cmd_Act::execute(Widelands::Game&) ()
 Widelands::Cmd_Queue::run_queue(int, int&) ()
 Widelands::Game::think() ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in widelands (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Hans Joachim Desserud (hjd) wrote :

Thanks for reporting.

Do you have a replay or perhaps savegame where this crash is triggered? If so, it would be useful if you could upload it so that someone can take a look at it.

I've marked this as also affecting Widelands, since it is unlikely this is specific to the packaging or Ubuntu. I tried to search for various crash bugs, since I know we had some crashes in the battle code which should be fixed in build19, but I didn't find an exact match.

tags: added: crash military
Revision history for this message
GunChleoc (gunchleoc) wrote :

Might be a duplicate of the following bug, which we also have trouble reproducing:

https://bugs.launchpad.net/widelands/+bug/1636966

So, if you should have an autosave for this, it would be a great help :)

Changed in widelands:
milestone: none → build20-rc1
importance: Undecided → Critical
Revision history for this message
Guybrush88 (guybrush) wrote :

these are the replays that might have the crash (I'm not sure about the exact one, since I played also other games that day, sorry about that)

Revision history for this message
GunChleoc (gunchleoc) wrote :

Thanks - I'm going through them now. If you still have any autosaves, that would be even better :)

Revision history for this message
Guybrush88 (guybrush) wrote :

I don't have the autosaves for such games anymore, I'm sorry about this :(

Revision history for this message
GunChleoc (gunchleoc) wrote :

Thanks for checking! Back to square one, then.

Revision history for this message
GunChleoc (gunchleoc) wrote :

I'll mark this as a duplicate now, since it's very likely that it's the same bug as mentioned in #7.

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.