lkml.org 
[lkml]   [2002]   [Dec]   [21]   [last100]   RSS-feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
Complete thread (EXPERIMENTAL)
/
SubjectRe: Valgrind meets UML
DateSat, 21 Dec 2002 11:05:25 -0500
FromJeff Dike <>
Digg This
jeremy@goop.org said:
The main problem will be that newly allocated memory will still be considered initialized by its previous owner. Also, if UML allocates memory using mmap, all memory will be considered to be initialized.

What I was doing was having kfree and free_pages set the freed object to noaccess. Presumably, that tells valgrind to consider the memory uninitialized.

Presumably, that will also cause errors from inside the allocator if it touches that memory at all before it's allocated again.
Jeff

\
ISP Services
Valid XHTML 1.0!\ /
Valid CSS! Last update: 2005-03-22 12:31    [W:1.674 / U:0.060 seconds]
©2003-2005 Jasper Spaans