Wesnoth 1.4 Windows binary crashes during game start

[Mist]

The design decision is to have support from anything running 486DX and Win98 upwards, that's why I'm trying to find out all the possible reasons for the problem you're experiencing.

I'll want to try few other things over the next few days, be prepared for a lot of weird questions and files to download
Do you know how to run gdb? It would be much easier (and faster) if I got a backtrace of the crash.

[Wesnothphile]

Glad to hear my system is within the design specs. Unfortunately, I don't know much about GDB, but I'll try to learn more about it.

[Mist]

This http://www.wesnoth.org/files/wesnoth_k63.zip is an exe with debug symbols built for your architecture. You need to download gdb from mingw.org, place gdb.exe in your wesnoth directory, and from commandline run :

Code: Select all

gdb.exe wesnoth
run

once wesnoth crashes run

Code: Select all

bt

Thi will output a stack backtrace, paste that output here.

[Wesnothphile]

Hi, Mist, your new exe worked wonderfully. It was able to run and not crash at the reading file/creating cache phase like the previous exes, so gdb said that there was no stack to backtrace.

I joined multiplayer and observed a game as well as a quick turn in a single player campaign. It didn't crash during any of these tests. So after ending Wesnoth, attempts to run backtrace got the response from gdb that there was no stack to backtrace, since there was no crash.

Whatever you changed seemed to fix the problem. Does this mean you've isolated and corrected the problem? Or do we still need to run some more tweaks and diagnostics to narrow down the search area and pinpoint whatever was causing the official binary to fail? I'll help test out other exes and do backtraces if they fail, if you need me to, so that we can identify the bug if you haven't already.

I'd hate to think a special optimized build would be required for me and others with similar systems during every new point release if we can't identify the bug, and it may be an unreasonable burden for the the windows binary packagers.

Thanks for all your hard work, Mist. I really appreciate the effort you've put into solving this issue and tracking down bugs in Wesnoth. You're amazing!

[Mist]

There is at least one more exe I'd like you to check, not because I don't know what's wrong ( your answer gave me all the info I needed) but to see if I'm still able to relase one-suits-all binary, or do I have to start doing separate ones for main CPU architectures, which will in turn force a rethink of packaging for windows.

Anyway, try this one. No symbols here, run normaly and just say if it works or not.

[Wesnothphile]

Yes, this one also works.