|
From: Nicholas N. <nj...@cs...> - 2005-09-11 23:02:21
|
On Sun, 11 Sep 2005, Oswald Buddenhagen wrote: > On Sun, Sep 11, 2005 at 10:58:29AM -0700, Robert Walsh wrote: >>> I'm interested both in whether this is fundamentally possible, and an >>> idea of what things would need to be done to actually implement it. >> >> I don't think this is possible. Valgrind creates a lot of state that >> wouldn't be around if it started half-way through the program > >> (e.g. memory validity information.) > > valgrind != memcheck. That's true, but it doesn't affect Robert's point, as there is lots of other state, and Valgrind very carefully controls many things so they are done in just the right way. > "attachabliity" might well be achievable for tools > that don't preclude it inherently. probably it depends on how flexible > the new memory manager will be in that regard. Not flexible enough, I predict. Attachability is not a design goal, it would require too many deep changes. Nick |