Valgrind status: 115 errors left

[Maarten Lankhorst]

Hi Dan,

2008/6/20 Dan Kegel <dank at kegel.com>:
> Changes since yesterday:
> - Added two patches by Huw, one by Roy
> - Removed one by Roy that's now in git
>
> This plus other improvements in git get us down to 115,
> rather a stunning improvement from a few days ago.
>
> Please join the party!  We can use all the help we can get
> getting rid of these bugs; though many are innocuous to users,
> a few aren't, and they're all annoying to anyone using valgrind.
>
> When you're running valgrind yourself, you probably want
> to run it like I do in
> http://kegel.com/wine/valgrind/runtest.patch
> with the  --workaround-gcc296-bugs=yes option
> (regardless of which compiler you use),
> else you'll see a warning about invalid stack use
> on each exception.
>
> Report showing unique nonleak errors:
> http://kegel.com/wine/valgrind/logs-2008-06-19.counts.txt
>
> Logs:
> http://kegel.com/wine/valgrind/logs-2008-06-19.log.gz
> http://kegel.com/wine/valgrind/logs-2008-06-19/
>
> Pending wine patches:
> http://kegel.com/wine/valgrind/logs-2008-06-19-patches/
> http://kegel.com/wine/valgrind/logs-2008-06-19-patches.tgz
> http://kegel.com/wine/valgrind/logs-2008-06-19-patch.txt
>
> Suppression file:
> http://kegel.com/wine/valgrind/valgrind-suppressions

Have you tried with --malloc-fill=55 --free-file=aa ? It is similar to
warn+heap, but it's valgrind compatible.

Cheers,
Maarten.