![]() | ||||||||||
Messages in this thread |
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | |||||||||
| Last update: 2005-03-22 12:31 [from the cache] ©2003-2008 | ||||||||||