#7110 Using coin into machine makes ScummVM 1.8.0 crash (Spanish version)

[Probador]

Using Drascula (Spanish version), loading the savegame i provide, using the coin into the machine (this is the second time i used the coin, after the first time it works well and you get tobacco), crash ScummVM in the third sentence the protagonist say. I am using ScummVM 1.8.0 on Win7 64 bits.

I downloaded the game from the official website (now the game is free):
http://www.alcachofashop.com/product_info.php?products_id=32&language=es

[Probador]

I tried spanish Drascula on Dosbox 0.74 and it does not crash, so looks like it is an ScummVM error

[Probador]

The bug does not happen in the english version of the game. Savegame attached

[Thierry Crozat]

Strange. I can't reproduce with version 1.8.0 on OS X. Could this be a Windows specific issue?
I first tried with the game data available on our web site since I already had them (http://www.scummvm.org/games/#drascula) and then to make sure I downloaded the ones from your link (and after checking they are binary identical to the ones we have).
With your save game it doesn't crash for me when I use the coin into the machine.

[Probador]

But did you try my spanish savegame or my english savegame? It only crashes with the spanish savegame (drascula-es.004)

[Thierry Crozat]

Yes, I used the Spanish version and your Spanish save game for all my tests.
But anyway, as I wrote in my following update, I did reproduce the crash on Windows with our official release (and only with that one).

[Thierry Crozat]

Some further tests: It does indeed crash with our Windows 1.8.0 release (I tried on Windows 10 64 bits). However it doesn't crash with the version I compiled myself or with the version from our buildbot (http://buildbot.scummvm.org/builds.html - although the stable version there is slightly more recent than 1.8.0). So it looks like this might be an issue with the way we compile the release build.

[kirben]

The problem only occurs when a release build is enabled on Windows, specifically only when optimizations are enabled in GCC 4.6.2 under MinGW. The problem is specific to GCC 4.6.2. under MinGW, and doesn't occur with GCC 4.9.3. under MinGW.

I attached a back trace if it is any use, some variables are optimized out though.