Important Dates

Latest Posts

Topic: Release 1.2

Forums » Widelands Development » Coding & Scripting » Release 1.2
hessenfarmer
Avatar
Joined: 2014-12-11, 23:16
Posts: 2724
Ranking
One Elder of Players
Location: Bavaria
Posted at: 2024-11-02, 10:21

tothxa wrote:

hessenfarmer wrote:

we have a reproducable bug in the windows 32 bit version that is really annoying.

Is this new to 1.2.1rc1, or also affects v1.2?

I could not test yet. Will be able to do that on sunday at the earliest.

Top Quote
tothxa
Avatar
Joined: 2021-03-24, 12:44
Posts: 460
OS: antix / Debian
Version: some new PR I'm testing
Ranking
Tribe Member
 Posted at: 2024-11-02, 15:28

hessenfarmer wrote:

getting a backtrace was not possible as the crash of the game was catched by our framework, which provided a error message.
or at least I do not know how to get a backtrace in this case with gdb.

Since you know the place of the problem, you should be able to set a breakpoint, and print the backtrace when the breakpoint is hit. Should be something like this (at least this works on linux):

break map.cc:2191
Top Quote
Nordfriese
Avatar
Topic Opener
Joined: 2017-01-17, 18:07
Posts: 2029
OS: Debian Testing
Version: Latest master
Ranking
One Elder of Players
Location: 0x55555d3a34c0
Posted at: Yesterday 09:57

We will not go to release today… face-sad.png

I found a reproducible desync in 1.2.1. To trigger, start a two-player LAN game on Fellowships with naval warfare enabled, no fog of war, and both starting positions set to Barbarians-Discovery, third player slot closed. It happens around gametime 1574 milliseconds. Am investigating, and when I find out how to fix, IMO we'd better have a second release candidate to be safe.

Top Quote
Nordfriese
Avatar
Topic Opener
Joined: 2017-01-17, 18:07
Posts: 2029
OS: Debian Testing
Version: Latest master
Ranking
One Elder of Players
Location: 0x55555d3a34c0
Posted at: Yesterday 10:33

Fix is up: https://codeberg.org/wl/widelands/pulls/4926

Edited: Yesterday 12:15
Top Quote