[r1249] Release compile of zdoom doesn't run

[Chris]

Those valgrind warnings are gone. Just this one remaining that ZDoom seems to be responsible for

Code: Select all

==17488== Use of uninitialised value of size 4
==17488==    at 0x826DC9E: R_InitSpriteDefs() (r_things.cpp:371)
==17488==    by 0x826DF8D: R_InitSprites() (r_things.cpp:889)
==17488==    by 0x82159B7: P_Init() (p_setup.cpp:3605)
==17488==    by 0x815D1AB: D_DoomMain() (d_main.cpp:2587)
==17488==    by 0x812C992: main (i_main.cpp:272)

Gibbing still doesn't work, though (I was about to post in that topic that it affects 32-bit Gentoo, too, before I started with Valgrind here).

[Graf Zahl]

Ok. I'll add a state dump command to ZDoom. As soon as the next revision is up please run it, enable the log and type 'dumpstates'. Hopefully that will yield some information.

[sniperchance]

Alright, I tried out the dumpstates command, and here's what I got.

zdoom-states.txt

(230.22 KiB) Downloaded 43 times

[Graf Zahl]

Was that on Windows or Linux?

[Chris]

I'm on Linux, and the log is the same as mine (diff shows no differences besides the start time of the log itself). So either he's on Linux/Unix, or there's no difference with Windows.

[Graf Zahl]

Ok, then the gibbing problem has nothing to do with my state code changes. My dump is exactly the same, too.

Closing this thread.

[sniperchance]

Even better, I was actually on Mac OS X.