[WIN] wideland dev builds crash during starting under WinXP

[Country_Man_G]

WinXP Sp3
Wideland v16 Release works without any problem

I uninstall WL
I install Widelands-bzr61xx-nomusic-win32.exe xx = 87..93

now WL start normally, but after the first mouse click on WL-Main-Windows a windows system message will shown "there are any problems ...." and WL crashed

I uninstall WL and install WL v16 Release the world is happy

The "over night builds" seems to have a bug when starting the games

[Hans Joachim Desserud (hjd)]

Thanks for reporting this. Is this the same bug which has been discussed on the forum recently (http://wl.widelands.org/forum/topic/652/)?

>a windows system message will shown "there are any problems ...." and WL crashed
That's a windows error message right, not from Widelands? Does it say anything more?

Also, could you please attach stderr.txt and stdout.txt which might contain error messages or other information. See Nasenbaer's suggestion for where they might be found on windows http://wl.widelands.org/forum/post/4086/

Really nice to know that build16 works fine. I assume something which has been changed since then is causing this, so I'm marking it as a regression. It would be nice (though not requireed of you) if you have the time to test some older builds to help us pin point exactly where this change occured.* If you (or someone else who can reproduce this problem) can help you don't need to check every single build. Based on the revision numbers between build 16 and latest pick one halfway in between, if that works; pick a build halfway between that and latest, if it doesn't; pick a build halfway between that and build 16. In other words, the same tactic as when guessing a number between 0 and 100, or binary search which is the proper name. :)

* I don't really know how feasible this is even, as I don't know if older development builds for Windows are "archived".

[Country_Man_G (newsgroup-mail)]

Ok ... I uninstall WL 16 release
=> nothing from WL is on fixdisk at this step
I install Widelands-bzr6194-nomusic-win32.exe
After the first Mouse-Click the WinXP-Message will shown "es ist ein .... blah blah"
The WL-Main-Window freeze
I look for stderr.txt => this file is empty
and in stdout.txt I found this:

Set home directory: C:\Dokumente und Einstellungen\Roland/.widelands
No version file found
There's no configuration file, using default values.
Adding directory:./.
No version file found
Adding directory:.
No version file found
Adding directory: C:\Programme\Widelands
No version file found
selected language: (system language)
SDL_VIDEODRIVER=&
Graphics: Trying Video driver: 0 windib SDL_VIDEODRIVER=windib
Graphics: Try to set Videomode 800x600 16Bit
Graphics: Setting video mode was successful
**** GRAPHICS REPORT ****
 VIDEO DRIVER windib
 hw surface possible 0
 window manager available 1
 blitz_hw 0
 blitz_hw_CC 0
 blitz_hw_A 0
 blitz_sw 0
 blitz_sw_CC 0
 blitz_sw_A 0
 blitz_fill 0
 video_mem 0
 vfmt 00adfc98
 size 800 600
**** END GRAPHICS REPORT ****
Graphics: flags: 0
[] Section [global], key 'EXENAME' not used (did you spell the name correctly?)
Sound_Handler: songset "intro" does not exist!
Sound_Handler: songset "menu" does not exist!

now I kill the WL-Main-window
=> end

[Tino (tino79)]

Hm, the problem is not caused by the missing music directory in my dev
builds. I just tested it on my system and also get the missing songset
messages, but widelands runs fine.
The next messages i have in my stdout.txt are:

selected language: (system language)
Sound_Handler closing times 1, freq 22050, format 32784, chan 2
SDL_AUDIODRIVER waveout

Please try the following:
- attach your wl config file here : C:\Dokumente und
Einstellungen\Roland\.widelands\config
- try to delete the config file and then start widelands

Regards,
Tino

2012/1/17 Country_Man_G <email address hidden>:
> Ok ... I uninstall WL 16 release
> => nothing from WL is on fixdisk at this step
> I install Widelands-bzr6194-nomusic-win32.exe
> After the first Mouse-Click the WinXP-Message will shown "es ist ein .... blah blah"
> The WL-Main-Window freeze
> I look for stderr.txt => this file is empty
> and in stdout.txt I found this:
>
> Set home directory: C:\Dokumente und Einstellungen\Roland/.widelands
> No version file found
> There's no configuration file, using default values.
> Adding directory:./.
> No version file found
> Adding directory:.
> No version file found
> Adding directory: C:\Programme\Widelands
> No version file found
> selected language: (system language)
> SDL_VIDEODRIVER=&
> Graphics: Trying Video driver: 0 windib SDL_VIDEODRIVER=windib
> Graphics: Try to set Videomode 800x600 16Bit
> Graphics: Setting video mode was successful
> **** GRAPHICS REPORT ****
>  VIDEO DRIVER windib
>  hw surface possible 0
>  window manager available 1
>  blitz_hw 0
>  blitz_hw_CC 0
>  blitz_hw_A 0
>  blitz_sw 0
>  blitz_sw_CC 0
>  blitz_sw_A 0
>  blitz_fill 0
>  video_mem 0
>  vfmt 00adfc98
>  size 800 600
> **** END GRAPHICS REPORT ****
> Graphics: flags: 0
> [] Section [global], key 'EXENAME' not used (did you spell the name correctly?)
> Sound_Handler: songset "intro" does not exist!
> Sound_Handler: songset "menu" does not exist!
>
> now I kill the WL-Main-window
> => end
>
> --
> You received this bug notification because you are subscribed to
> widelands.
> https://bugs.launchpad.net/bugs/917250
>
> Title:
>  wideland crashed during starting under WinXP
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/widelands/+bug/917250/+subscriptions

[Country_Man_G (newsgroup-mail)]

1. I modify line in config
    disable_fx="true" => crashed
2. I delete config file
    => crashed

note:
I have an old intel main board (about 7 years old) with audio chip on board,
but now I have not connected any loadspeaker

[Country_Man_G (newsgroup-mail)]

After a discussion in tech. forum her the last infomation:

3. in config file

# Automatically created by Widelands build-16 (Release)

[global]
disable_fx="true"
disable_music="true"

=> crashed after the FIRST mouse click on desktop

stderr.txt is empty

stdout.txt:

Set home directory: C:\Dokumente und Einstellungen\Roland/.widelands
No version file found
Adding directory:./.
No version file found
Adding directory:.
No version file found
Adding directory: .....shorten....C\Programme\Widelands
No version file found
selected language: (system language)
SDL_VIDEODRIVER=&
Graphics: Trying Video driver: 0 windib SDL_VIDEODRIVER=windib
Graphics: Try to set Videomode 800x600 16Bit
Graphics: Setting video mode was successful
**** GRAPHICS REPORT ****
 VIDEO DRIVER windib
 hw surface possible 0
 window manager available 1
 blitz_hw 0
 blitz_hw_CC 0
 blitz_hw_A 0
 blitz_sw 0
 blitz_sw_CC 0
 blitz_sw_A 0
 blitz_fill 0
 video_mem 0
 vfmt 00add0e8
 size 800 600
**** END GRAPHICS REPORT ****
Graphics: flags: 0
[] Section [global], key 'EXENAME' not used (did you spell the name correctly?)

[Nasenbaer (nasenbaer)]

stupid, but still valid question: may it be, that the development builds from Tino are missing a dll file, that the build16 version add with it? or maybe a library is outdated? Further libboost is finally needed as dll as well, but I don't know the exact name of the dll that is needed, so it is more or less try and error.

Maybe... could you please try to run Widelands using gdb or another debugger?

[Country_Man_G (newsgroup-mail)]

I program with c++builder from embaradero and I don't and other debugger.

I can check the dependency of the exe, but I have no idea what I should search for ?
and I have no idea how wideland work intern, because I check/play with wideland to
see all features from old to new are available, and then I draw new maps.

[Nasenbaer (nasenbaer)]

Sorry, I do not know that c++builder, I don't even use Windows any longer. However my main idea was, to start Widelands inside a debugger environment - once Widelands crashes the debugger will be able to at least give a hint to where the problem resides.

[Country_Man_G (newsgroup-mail)]

I try to get more information with Windbg v5.00.2195.11 from Microsoft
 - start debugger
 - open wideland.exe
 - go
 > many dll will loaded and also App01.exe and App02.exe
 > before crash
    all DLL's loaded from ../wideland/...
    module load msacm32.drv and dll (win/system32) => ok
    module load midimap.dll (win/system32) => ok
    module load jpeg.dll (win/system32) =>
 >> now I see this first Windows (desktop with Wideland logo)
 =============================
 when I click with the mouse on this first view
  ==>> application crashed
  > the debugger try to load symbols for sdl_gfx.dll
  > debugger break and show
     > First change exception c000001d (Illegal Instruction) occurred
     > Thread stopped

Sorry ... more infomation I cannot see in debug logging output

[Country_Man_G (newsgroup-mail)]

form discussion forum here the last note:

AppName: widelands.exe AppVer: 0.16.0.1 ModName: sdl_gfx.dll
ModVer: 0.0.0.0 Offset: 0000fde9
Exception Information Code: 9xc000001d Address: 0x6a0cfde9

[Shevonar (shevonar)]

In the dump file you uploaded a SbieDll.dll is included. Are you running Widelands in a Sandboxie sandbox? I tried it myself and once Widelands crashed when I changed the resolution to fullscreen. However I couldn't reproduce this, so we are not much further :S It it is possible that Widelands shows some strange behavior within a sandboxed environment. Could you check that the same problem occures when you run Widelands not in the sandbox?

[Country_Man_G (newsgroup-mail)]

Yes ... wideland runs windowed in a sandbox

Note:
 - WL v16 Release will work without any problems in the same environment
 - after Widelands-bzr61xx-nomusic-win32.exe with xx > 84 WL crashed

[David Allwicher (aber)]

Do you blame commit bzr6185, that something which happened at that point to the source or the build environment broke widelands in a way that it is impossible to start it up inside your sandbox?

[Country_Man_G (newsgroup-mail)]

sorry I have not backuped all working versions of WL.

have you an archive where I can download the older versions, then I will download and try it to find to point (version) where the crash series begin

[Country_Man_G (newsgroup-mail)]

I try also Widelands-bzr6240-nomusic-ggzreplacement-win32.exe => the same problem

[Country_Man_G (newsgroup-mail)]

We discuss this problem also in the technical forum ... the lastest info's

from Tino:
  Please try one more version:
  http://widelands.8-schuss.de/Widelands-bzr6218-nomusic-win32.exe
  I've updated nearly all DLL files...

from me:
  Ok ... I download this version and try it => crashed !

my next steps:
   I install WL 16 release parallel ... it works fine.

   Then I copy WL6218.exe in the folder of WL16release.

   after starting the a dll is missing or wrong ...
   copy this DLL ...
   I to this until SDL_gfx.dll is copied => crashed

I think their is a basic system method changed in a version and after this point there is this problem.

The point of the crash is always the same:

After starting WL I can see the first Screen with the background picture, at the buttom of this Screen is the Text "Drücke ESC oder benutze die Maus ....", after pressed ESC or clicked with the mouse => crashed after about 5 Seconds

[Country_Man_G (newsgroup-mail)]

Important NOTE:

I install also the Version 6218 at C:\ direct without Sandbox, Internet Gateway, Firewall => crashed !!!

Maybe problems with the hardware ?

My graphic card is a Matrox Millennium P650

[fuchur (fuchur77)]

I have the same problem, unfortunately I don't know the last working build. But it definitely occurs with build 6176 (and also the latest 6227). Maybe I can find an older working build somewhere on my external harddisk. The error code is the same as in comment #10.

System is WinXP SP3, Notebook, ATI Mobility Radeon 7500 (32 MB), onboard sound

[Shevonar (shevonar)]

Since this seems to be not a single case, we should fix this for build17. Maybe the problem is a too new sdl version rather than a too old one. Unfortunately none of the developers can reproduce the bug, so it is hard to find a quick solution.

[Astuur (wolfsteinmetz)]

I don't know if this is in any way helpful, but I never used anything but Tino's "overnight" versions and I have never seen
this bug at all. The official build16 also worked until I uninstalled it.
WinXP SP3 here too, no notebook, no sandbox, and the graphic card is an Nvidia Geforce 275
I use mouseclick or ESC interchangebly at the point in question.

[fuchur (fuchur77)]

Build 16 works also fine for me, and I also use Tino's versions. Unfortunately I can't reproduce since which build the problem occurs.

One thing I observed was that the first time I installed a "non-working" version I didn't even come to the starting screen with the message "press ESC or click the mouse". The windows error came before. Only when I renamed the config file to config.old I saw that starting screen and the crash happend after clicking the mouse. I had the previous working installation configured to run in full screen mode. So the new installation used the old config file an tried to start up in full screen mode, too. And crashed immediately. After renaming the config it started in windowed mode and crashed one step later.

[Tino (tino79)]

Hm, as Country_man_G stated in #9, there is a jpeg.dll from his system32 folder loaded. But widelands should load libjpeg-8.dll from it's own directory.
Can you try:
- open a console (cmd.exe)
- cd into your widelands directory
- set PATH= (this should reset your path variable temporarily for the console)
- widelands.exe

Or another way would be to rename jpeg.dll into e.g. jpeg.dll.bkp for a short test.

[Country_Man_G (newsgroup-mail)]

Ok ... I renamed jpeg.dll to _jpeg.dl_ => the same => crashed

[fuchur (fuchur77)]

The reset of the path variable doesn't change anything for me. Especially as I don't have a jpeg.dll in my system32 folder. The only place where I find a jpeg.dll is in the widelands folder.

The only positive thing I can tell is that Widelands-bzr6088-nomusic-win32.exe runs without problems. I also tried Widelands-bzr6169-nomusic-win32.exe which crashes. Unfortunately I don't have a setup of a build in between. If someone could provide one I'd like to test it.

I compared the stdout.txt files of both versions and found one difference in the graphics report section:

 vfmt 00a7a720 (crashing build 6169)
 vfmt 003e9d68 (running build 6088)

In the folder of build 6169 exists a stderr.txt file but without content (size 0 bytes). Maybe widelands crashed before any output to stderr was generated. Or it is not flushed to file immediately.

Then I compared the installed dll files of builds 6088 and 6169. Maybe this can help.

- Different dll files:
glew32.dll
libexpat-1.dll
libiconv-2.dll
libintl-8.dll
lua51.dll
SDL_net.dll
zlib1.dll

- same dll files:
jpeg.dll
libfreetype-6.dll
libggz-6.dll
libggzcore-10.dll
libggzmod-6.dll
libogg-0.dll
libvorbis-0.dll
libvorbisfile-3.dll
SDL.dll
SDL_image.dll
SDL_mixer.dll
SDL_ttf.dll

- dll files new in 6169:
libgcc_s_dw2-1.dll
libpng-3.dll
lua5.1.dll
SDL_gfx.dll

- dll files in 6088 but not in 6169:
libintl.dll
libSDL_gfx-13.dll
libtiff-3.dll

[Nasenbaer (nasenbaer)]

I can't say a lot about the bug itself, but:

* all libggz*.dll files and the libexpat-1.dll can be removed, because we do not use ggz anymore
* libintl.dll should definitely be in the newer setups as well. This is needed for translations in game.

[fuchur (fuchur77)]

I copied the libintl.dll to the folder of build 6169, but that didn't change anything. Well, I didn't expect to as nobody using Win7 complained about not running setups or missing dll files.

[Gabriel Margiani (gamag)]

My Brothers and I tried rev 62445 on wine, win7 and winXp and it crashed
only under winXp.

We got an error message like that one in #10 so we replaced
SDL_gfx.dll by that one of build 16. (they differ in size, name and version)

Now it stared and we could play, but in opengl mode we got no terrain texture
(everything white, expect of some textured triangles).

[Gabriel Margiani (gamag)]

Sorry, we tried rev 6245 not 62445

[Country_Man_G (newsgroup-mail)]

I read the lastest note #27 and try this:

 - install bzr6252

=> start ... click ... crash

 - delete SDL_gfx.dll in v6252
 - rename libSDL_gfx-13.dll from v16 Release in SDL_gfx.dll
 - and copy this file to v6252

=> start ... and play ... without any problems

[fuchur (fuchur77)]

I tried the same with build 6169 and the libSDL_gfx-13.dll from v16, started without problems.

I also enabled OpenGL and it worked. But maybe there have been major changes so that the behaviour in latest builds might be different.

[Tino (tino79)]

Hey, thank you for all the testing. So SDL_gfx sems to be the cuplrit.
I've compiled the last three versions (2.0.20/21/22 , my builds contain 2.0.23):
http://widelands.8-schuss.de/SDL_gfx_20.zip
http://widelands.8-schuss.de/SDL_gfx_21.zip
http://widelands.8-schuss.de/SDL_gfx_22.zip

Could you test each of them with the latest build?
http://widelands.8-schuss.de/Widelands-bzr6256-nomusic-win32.exe

This should give us a clue if the problem on XP is caused by a change in SDL_gfx or some binary incompatibility between the VS-compiled main SDL.dll we ship and my with mingw compiled SDL_gfx.dll.

[fuchur (fuchur77)]

Unfortunately the latest build itself doesn't start. And replacing the DLLs by the ones you provided didn't help.

Only using the libSDL_gfx-13.dll from build 16 works. Is there anything else I could test?

[Gabriel Margiani (gamag)]

I had the same results than fuchur ...

[fuchur (fuchur77)]

I tried to profile widelands with Depency Walker, a tool to show all procedure calls of a program and the used DLLs. But I don't know how the result can help. I tested the working and the crashing version of sdl_gfx.dll. There is only one difference in the output, namely the crash.

This event occurs right after libjpeg-8.dll is loaded by sdl.dll. The loading is ok, then there are several GetProcAddress calls for functions of libjpeg-8.dll which are ok. One GetProcAddress call in NTDLL.dll (ok). Then the exception:

First chance exception 0xC000001D (Illegal Instruction) occurred in "c:\programme\widelands\SDL_GFX.DLL" at address 0x6A0D1374.
Second chance exception 0xC000001D (Illegal Instruction) occurred in "c:\programme\widelands\SDL_GFX.DLL" at address 0x6A0D1374.
Exited "c:\programme\widelands\WIDELANDS.EXE" (process 0x328) with code -1073741795 (0xC000001D).

I can't see any hint on the problem in the output of the working sdl_gfx.dll. There are just actions shown which are related to exit widelands by clicking on exit game (or whatever this button is labeled in english).

[Country_Man_G (newsgroup-mail)]

note for #31

I try the daily lastest version, now WL crashed directly without any click or keypressed

No version of SDL_gfx_XX will run !

Only the renamed version of libSDL_gfx-13.dll will running.

[Tino (tino79)]

Ok, i've now a Windows XP SP2 available as VirtualBox Image.
First thing:
A recent build didn't start at all. But the reason was the lua.dll. After installing LuaForWindows (http://code.google.com/p/luaforwindows/downloads/list) Widelands runs like a charm.

The Lua dlls seem to depend on Microsoft Windows Visual C++ Redistributable 2005 which gets installed by LuaforWin.
You could do me a big favor and install LuaForWin and do a test if Widelands bzr6263 runs with it.

I'll try to compile Lua on my own in the meanwhile, to get dlls with no dependencies...

[Tino (tino79)]

Ok, i've packaged a new version with a from source compiled lua bib.

=> http://widelands.8-schuss.de/Widelands-bzr6267-nomusic-win32.exe

Please test.

This includes no lua*.dll at all, it seems it gets statically linked. I was able to run this on XP without any problems.

[Country_Man_G (newsgroup-mail)]

I try it with 6267 => ALWAYS the same => CRASHED

My may to do the test:
 - uninstall last version
 - delete the folder
 - install 6267
 - start WL => click => crash

 - save SDL_gfx.dll
 - copy libSDL_gfx-13.dll from WL16 release
 - and rename to SDL_gfx.dll
 => WL will start => no problems

 additional test
1)
 - default is the screen 800x600 pixel
 - directly after install 6267 start => crash will seen after click or keypressed
2)
 - start 6267 with renamed libSDL_gfx-13.dll
 - change screen to 1024x768 pixel
 - delete renamed libSDL_gfx-13.dll
 - backup the SDL_gfx.dll from 6267
 - start 6267 => now crash will seen WITHOUT any click or keypressed

[fuchur (fuchur77)]

I installed 6267 on a clean XP SP3 in a virtual machine and it runs fine. I'll try this evening at home on my native XP machine.

[fuchur (fuchur77)]

Bad news, on my native XP machine the new version 6267 crashed. As usual I got to the first screen, clicked the mouse and bang! When I replaced the SDL_gfx.dll by the old one of build 16 it runs fine.

I tried to disable OpenGL, but that didn't change anything.

@Country_Man_G
The moment of the crash depends on the window mode. If widelands is in fullscreen mode it will crash immediately whithout showing any starting screen. In window mode the crash occurs after you click in the starting screen.

[Jari Hautio (jarih)]

This sounds really strange, that clean winxp3 machine works, but real machine not. I also tried in vm, and had no problems with recent build. My first guess would be that there's a wrong dll loaded outside widelands package - or one with different C-runtime. Then there might be something wrong in the build environment where SDL_gfx was built.

To sort out, if problems is related to different compilers in the different dlls, try rebuilding all libraries with mingw using source package from lp:~jarih/+junk/wl-3rdparty-src. There's a helpful build script for rebuilding all sources with msys/mingw. It's complete source package that has no external dependencies. BuildingWidelands wiki page has full info on building the libs.

[Gabriel Margiani (gamag)]

I cross compiled SDL_gfx on Linux using mingw.
Using this dll I could run widelands without problems
on XP.
I tried the same with SDL.dll.
old sdl_gfx.dll + old sdl.dll => crash
old sdl_gfx.dll + my sdl.dll => crash
my sdl_gfx.dll + old sdl.dll => works fine
my sdl_gfx.dll + my sdl.dll => works fine

[Gabriel Margiani (gamag)]

I attached my SDL_gfx.dll, if somebody wants to test ...

[fuchur (fuchur77)]

Thanks, Gabriel, I tried your SDL_gfx.dll with build 6256 and build 6297, it works fine with both of them.

[Tino (tino79)]

I suspect some compiler flags causing this. I am using the "Makefile.mingw" to compile SDL_gfx with gcc 4.6.1.

Can you perhaps try the attached dll? I lowered -03 to -02...

Or some pro could identify some other problematic setting:

CFLAGS = -O2 -march=athlon-xp -mmmx -msse -m3dnow -DBUILD_DLL -DWIN32 -I$(include_dir)/SDL

[fuchur (fuchur77)]

Tino, this DLL works fine for me.

[Country_Man_G (newsgroup-mail)]

I work with a WL 6289 and the rename older SDL_gfx ....

now I downloaded the DLL (#43) and overright the older renamed version

=> perfect ... WL runs fine

[Jens Beyer (qcumber-some)]

I can remember reading somewhere (probably in the Gentoo environment) that for a stable system, -O3 is not recommended, and people should use -O2 at most.

I guess we should try to use -O2 at least for all builds which are done
1) for more people than just yourself (read: all packagers)
2) for people who don't know what they are doing (read: all users of compile.sh).

Knowledgeable developers will also know how to change this to -O3 if they want so.

[Tino (tino79)]

Country_Man_G, could you please also test my dll from #45 ?
Or the complete package: http://widelands.8-schuss.de/Widelands-bzr6309-nomusic-win32.exe

[Gabriel Margiani (gamag)]

I used -O3 to build my dll (#43).

But your (#45) dll works fine!

[Tino (tino79)]

Ok, i'll set this then to resolved for now. Perhaps it is also the combination of my gcc version and -03 which leads to the error and the next gcc update will again allow -03.

[Country_Man_G (newsgroup-mail)]

@#49

Ok ... I installed bzr6309 => it work's fine