crash in last bastion

[Klaus Halfmann]

I played last bation on Windows10 once which was fine but I was nable to conquer the enemey as of the design of the wap.

I then tried again but ran into an almost immediate crash.

I picked this version from appvoyer
_widelands_dev_widelands_bug_1687100_reveal_fields-2268_Debug_x86

[GunChleoc (gunchleoc)]

Looks like it might be network related, so assigning to Notabilis.

[Notabilis (notabilis27)]

Unfortunately, I cannot reproduce this crash. The savegame is working fine for me. I also don't know whether it is related to network. The game was started over the metaserver but the stdout looks normal.
Can you provide an stderr.txt file? It should be next to the stdout.txt. But I fear it might have been overwritten by later games. Are you able to reproduce this crash?

[Klaus Halfmann (klaus-halfmann)]

* I can reproduce this every time, did you use the version from appvoyer?
  This one: https://ci.appveyor.com/project/widelands-dev/widelands/build/job/ojby76dg8yc08797
* Do you use win64?

* There is no stderr.txz next to the stdout (I will try --verbose)
* I can try on the Ubuntu bultinto windows.

I actually downlaoded visual studio and was able to debug it there,
but only got some assembler code, which did help me either.

anbody around that can anaylze these .wer files?

Tino: you are our windows export, no?

[Notabilis (notabilis27)]

I am not using the AppVeyor-Build since I am under Linux. I used the same branch, though, but compiled it myself.

A shame that there is no stderr.txt. I thought it should be there. Unfortunately, I have no idea what to do with a .wer file. But it is great that the error is reproducible.
When you say "debug": Does that mean that you got any file/line number for the crash? That would be helpful.

If you are willing to try some stuff:
- Are you doing anything when it crashes?
- Does it also happen when you load the savegame as a LAN game?
- Is the crash always happening after the same time? Can you influence the time of the crash by setting the game speed?
- Does the crash also happen with other branches (e.g. trunk)?

[Klaus Halfmann (klaus-halfmann)]

>I tried this now with an "Ubuntu on Win10" build for bzr8373[bug-1687100-reveal_fields]
See https://wl.widelands.org/wiki/BuildingWidelandsWIN10/
(took some time, especially as bzer was hanging around for like 30 minutes for no reason).

I copied the save file but there it was running without Problems.

> - Are you doing anything when it crashes?
I just press "Pos1" to scroll to my starting postion then it crashes.
I will use 'c' and 's', too.
I tried fullscreen and windows, no change
(with Visual studio I am now asked if I want to debug, but no better results)

> - Does it also happen when you load the savegame as a LAN game?
Yes at exactly 03:03 game time,

> - Is the crash always happening after the same time? Can you influence the time of the crash by setting the game speed?
Tricky, as the save starts at 03:00 here is not much time for a speedup,
I came upto 5x at 03:04 when it crahed again. (Did not use 'c' and 's').

> - Does the crash also happen with other branches (e.g. trunk)?
must wait for the next appvoyer build (and stash this verion away ...)
I see a new version _widelands_dev_widelands_travis_osx is
Queued so I must wait some time.

I will tried to build widelands with visual Studio, but might first naive aproache failed:
I must setup subprojects for the libraries. So I have to dig deeeper into these structures,
first.

All that said I must assume its realred to the compiler/environment used on windows (10)
e.g. you may try to switch from clang to gdb (or whatever appvoyer uses), But still
the ABI is different.

I will assign this to tino now, perhaps he can reproduce its.

P.S. next time stay in the lobby, so we can chat there :-)

[Klaus Halfmann (klaus-halfmann)]

Tino: cn you reproduce this on win10? and get some debug output?

[Klaus Halfmann (klaus-halfmann)]

appveyor uses:
-- Check for working C compiler: C:/msys64/mingw64/bin/gcc.exe
-- Check for working CXX compiler: C:/msys64/mingw64/bin/g++.exe

[Klaus Halfmann (klaus-halfmann)]

Tried again with bzr8400[trunk] from https://widelands.8-schuss.de/
(There is a release build only...)

Does not happen there either.

OK Lets wait until this bug-1687100-reveal_fields branch has maded it into trunk.

Sorry for the fuzz.

[Klaus Halfmann (klaus-halfmann)]

Did some network gamin with Notabilis, 1st try took a bit longer, Notabilis plaiyng the AI part.
perhaps 03:08.

A 2nd ry made it crash at 03:03 again, where Notabilis was specator.

So maybe the "Other side", the AI made it crash.

The Assertion found in #1704449 happend in this config, too. But only sometimes.

[GunChleoc (gunchleoc)]

Don't wait for reveal fields to hit trunk - its still waiting for a code review.

Since we now suspect the AI, can you try he following build: https://ci.appveyor.com/project/widelands-dev/widelands/build/master-2253

[Klaus Halfmann (klaus-halfmann)]

Uhm, that did not work:

This is Widelands Version master-2253_Debug_x64 (Debug)
...
UnhandledVersionError: Dieses Spiel wurde mit einer inkompatiblen Widelands-Version gespeichert und kann deshalb nicht geladen werden.

Packet Name: GamePlayerAiPersistentPacket
Saved Version: 3
Current Version: 2

will try to play it from scratch ... later

[Klaus Halfmann (klaus-halfmann)]

I will close this one now, If I ever see it again on some trunk like build,
it will reappear.