![]() | ||||||||||
Messages in this thread |
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 - 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 11:31 [W:0.150 / U:0.050 seconds] ©2003-2008 Jasper Spaans | ||||||||||