On Sat, 2005-08-13 at 22:35 +0000, Stefan Dösinger wrote:
Am Samstag, 13. August 2005 19:34 schrieb Lionel Ulmer:
This looks like a really nasty heap corruption to me, and I'm afraid it's beyond my knowledge. Can anyone of the ddraw/d3d people help me?
I think best would a +ddraw,+heap,+relay,+tid,+seh trace to be able to see where the corruption may occur. And it's not because it crashes into DDraw code that it's DDraw responsible for it :-)
This is interesting: Setting the +heap trace flag sets the bad address realiably to 0xaaaaaaaa(without my changes to DDraw). Does this say anything?
Looks like an uninitialized value to me. I've seen similar cases like that, and that's what it was.
Stefan
James