On Wed, Sep 23, 2009 at 10:43 AM, Israel Lins Albuquerque <[email protected]> wrote: > That's works fine for me too, but I can't see the purpose for this... > I can't see benefices to this option don't stay always on!
I need it off, and in fact I turn even more off, see https://bugs.kde.org/show_bug.cgi?id=201170 I build with that patch and use --show-possible=no to avoid generating gigabytes of warnings of questionable utility. So, the short answer is: big apps that are trying to stamp out all their memory leaks often need to focus just on the smallest set of highest value memory leak errors to keep from drowning. ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
