8 Nov
2007
8 Nov
'07
8:46 p.m.
"Dan Kegel" <dank(a)kegel.com> wrote:
I've updated http://kegel.com/wine/valgrind/ Today's results are at http://kegel.com/wine/valgrind/20071103/
The only difference from yesterday is I've added suppressions for the most common memory leaks, on the theory that it's easier to see the module-specific leaks that way.
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). There is also one memry leak reported, but I couldn't figure out the reason of that one. -- Dmitry.