http://bugs.winehq.org/show_bug.cgi?id=9916
--- Comment #22 from Dan Kegel dank@kegel.com 2007-10-31 02:02:31 --- I've been submitting patches to fix valgrind warnings lately, e.g. http://www.winehq.org/pipermail/wine-patches/2007-October/046005.html http://www.winehq.org/pipermail/wine-patches/2007-October/046006.html http://www.winehq.org/pipermail/wine-patches/2007-October/046007.html
To reproduce my results, apply http://wiki.winehq.org/Wine_and_Valgrind?action=AttachFile&do=get&ta... to a fresh valgrind-3.2.3 tree and install it, then apply http://wiki.winehq.org/Wine_and_Valgrind?action=AttachFile&do=get&ta... to your wine tree and build it, then run the tests under valgrind with RUNTESTS_USE_VALGRIND=1 make -k test > log 2>&1 A full run takes half the day, so run on just one subdirectory for starters. You probably want to look at the log after a couple minutes. If you see lots of spurious errors (e.g. in ld.so or Xlib) just copy the suppressions from the log file into tools/valgrind-suppressions and rerun. (If that helped, please email me your new suppressions file and I'll update the patch.)
I find it easier to analyse the results with the perl script included in the wine patch above, perl tools/valgrind-split.pl log but maybe that's just me.
Now that I've cleared out the first few easy errors, some interesting ones are starting to emerge. Give it a try!