Bug in the heap management code?

[Michael Günnewig]

Mike Hearn <mike at theoretic.com> writes:

> This is very much like a problem I am having with InstallShield.
> Something, somewhere, is trashing the heap data structures, which causes
> a crash some time later, often yards away from the original bug. As far
> as I know, there is no good way to spot this problem, it's just C/C++
> sucking.... maybe valgrind might help?

Yes and no. valgrind still doesn't support many instructions...

Have set and exported __GL_FORCE_GENERIC_CPU=1 else it will crash much
earlier. Seems to me that the native DLLs which I need to run
Morrowind contains some non-486 instructions. Does anyone knows
whether it's possible to tell these DLLs that we only have a 486 ?

Output of valgrind is attached.

  Michael

-------------- next part --------------
A non-text attachment was scrubbed...
Name: valgrind.log.gz
Type: application/x-gzip
Size: 6739 bytes
Desc: Morrowind-valgrind.log.gz
Url : http://www.winehq.org/pipermail/wine-devel/attachments/20030919/292988f3/valgrind.log.bin