Page 2 of 2
Re: [r1249] Release compile of zdoom doesn't run
Posted: Sun Oct 05, 2008 1:14 pm
by 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).
Re: [r1249] Release compile of zdoom doesn't run
Posted: Sun Oct 05, 2008 2:40 pm
by 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.
Re: [r1249] Release compile of zdoom doesn't run
Posted: Sun Oct 05, 2008 6:10 pm
by sniperchance
Alright, I tried out the dumpstates command, and here's what I got.
Re: [r1249] Release compile of zdoom doesn't run
Posted: Mon Oct 06, 2008 12:59 am
by Graf Zahl
Was that on Windows or Linux?
Re: [r1249] Release compile of zdoom doesn't run
Posted: Mon Oct 06, 2008 1:11 am
by 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.
Re: [r1249] Release compile of zdoom doesn't run
Posted: Mon Oct 06, 2008 1:41 am
by 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.
Re: [r1249] Release compile of zdoom doesn't run
Posted: Mon Oct 06, 2008 2:23 am
by sniperchance
Even better, I was actually on Mac OS X.