On Nov 8, 2007 6:46 PM, Dmitry Timoshkov dmitry@codeweavers.com wrote:
I looked at the vg-user32_win.txt warnings, and most of them are triggered by test_gettext() which intentionally passes an invalid memory address to SendMessage(WM_GETTEXT).
OK, I'll add a suppression for that.
BTW tests/win.c seems pretty racy. It fails strangely with warn+heap and differently strangely under valgrind. Under Valgrind, I bet the test is just bad at running really slowly. No idea why it fails with warn+heap, which doesn't seem too slow.
There is also one memry leak reported, but I couldn't figure out the reason of that one.
I'm not so worried about those, a leak's not as bad as a wild pointer, and it's probably just a missing free or close or something in the test code. But thanks for looking. - Dan