valgrind results updated
dmitry at codeweavers.com
Thu Nov 8 20:46:47 CST 2007
"Dan Kegel" <dank at kegel.com> wrote:
> I've updated
> Today's results are at
> 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.
More information about the wine-devel