Re: Valgrind meets UML

[Jeff Dike <jdike@karaya.com>]

jreiser@BitWagon.com said:
> I suggest that useful partial progress can be made sooner by
> identifying the allocators, telling valgrind about them and their
> external semantics, and having valgrind trust them.  

This is likely what will happen anyway.  It will likely generate noise
from inside the allocators until they are described.

> In particular, do
> not valgrind allocators at first.

This isn't possible without performing surgery on valgrind.  It has no idea
what's considered an allocator and what's not.

> Waiting for the globally correct description can take a long time,
> perhaps about as long as waiting for the authors of device drivers to
> update to a new device I/O model.

Nonsense.  They aren't going to be that complicated, and they don't change
very often anyway.

				Jeff