valgrind for WINE
Dimitrie O. Paun
dpaun at rogers.com
Wed Apr 2 06:55:33 CST 2003
On April 2, 2003 08:55 am, Adam Gundy wrote:
> the reason msvcrtd is there is that you need to use it for valgrind to do
> any checking of the heap - an instrumented malloc (see the changes to
> ntdll/heap.c) is required to tell valgrind that freshly allocated blocks
> are uninitialized, and the freed blocks are now invalid.
What Eric meant is that the msvcrtd can go in as a separate patch. Yes,
it is required by VALGRIND, but it's useful on it's own as well, so just
submit that one individually.
> maybe, this was just a hack to make it easier to use "in tree". not sure
> people would want a "--valgrind" switch in a (presumably) production
> winelib piece of software - it would show the world all your bugs ;-)
We can disable that switch completely if we don't configure with VALGRIND.
No problem there.
More information about the wine-devel