|
From: Bryan M. <om...@br...> - 2006-03-12 16:36:36
|
Dennis, thanks for the suggestion - I personally think it is an excellent idea. The only way to make something like that work without drowning in the output of 10,000 free()d pointers would be to introduce a new client request to mark the memory block after it is created. As each tracked pointer is then added or removed, a trace report could be generated. If I get enough interest in this tool, I will look to implementing this as a feature before the 1.0 release. thanks, Bryan "Brain Murders" Meredith Dennis Lubert wrote: > Am Sonntag, den 12.03.2006, 15:32 +0000 schrieb Bryan Meredith: > >> Omega addresses what I perceive to be one of the few shortfalls of the >> excellent Valgrind Memcheck Tool - where Memcheck reports the location >> that a leaked block was allocated, Omega also shows where it was leaked. > > Not that its bad to do that, but I think its better to say "Omega shows > also where the last pointer/reference to the allocated memory was lost". > Saying "I know were the memory was leaked" would imply to infer the > ownership of the object for the cases multiple pointers refer to it. Who > knows, maybe the pointer that would have been the one responsible to > free the memory has been lost way before another one that has been > copied around is lost. > So, maybe Omega could be extended to give (optional of course) reports > on where pointers to that memory were lost, in order to better figure > out where you should have freed it. > > greets > > Dennis > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > |