On Tue, Dec 04, 2007 at 04:46:36PM -0800, John Reiser wrote:
> It's up to the point of user mode for process 1; see log below.
> That means much of initialization, annotating the slab allocator
> (kmalloc) enough to "hide" the allocation structures from outside access
> but allow the allocator to reference them itself, and enough changes
> to valgrind to tolerate more forms of clone() and to handle switching
> stacks via longjmp(). I sent my changes for valgrind-3.2.3 to
> valgrind-developers last weekend.
Neato, that's further than I ever managed.
Jeff
--
Work email - jdike at linux dot intel dot com
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
User-mode-linux-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
