valgrind for WINE (part 2 - uninitialized memory fixes)

[Adam Gundy]

the attached patch fixes several uninitialized memory errors found by
using valgrind with WINE. there are hundreds (if not thousands) of other
bugs that still need fixing!

there is also a slight fix to the loader which marks executable sections
of PE images as read-only once imports have been fixed up.

you should apply this patch if you intend to use valgrind with WINE - it will
(slightly) reduce the number of error reports you get...

all of these fixes are for bugs in WINE - maintainers please commit to CVS.


Seeya,
 Adam
--
Real Programmers don't comment their code. If it was hard to write,
it should be hard to read, and even harder to modify.
These are all my own opinions.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wine-valgrind.patch.fixes
Type: application/octet-stream
Size: 13733 bytes
Desc: not available
Url : http://www.winehq.org/pipermail/wine-patches/attachments/20030328/c84722a3/wine-valgrind.patch.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wine-valgrind.clog.fixes
Type: application/octet-stream
Size: 1455 bytes
Desc: not available
Url : http://www.winehq.org/pipermail/wine-patches/attachments/20030328/c84722a3/wine-valgrind.clog.obj