On Thu, 7 May 2009, John Reiser wrote: >> - The last place where a pointer to a block was clobbered/lost, which >> is a probable location for the actual leak > > Search the Web for "valgrind omega".
Ouch, it's even in the valgrind distribution, although disabled by default and undocumented in the wiki. And Google is almost impossible to get to come up with it. The implementation is similar to my thoughts, but in a working stage. I guess I had already suspected what I proposed was not all that new :-) Yes, this does seem to be exactly what I had in mind, although it does not seem to provide the "last-used-at" location, which might also be very useful. I'll see if I can try it out. The main issue is that omega seems to be collecting quite a bit of dust now. Pity... Regards, Theodoros Kalamatianos ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
