Hi Dan, Just augmenting your response, I hope you don't mind. On Fri, 2009-10-16 at 17:33 -0700, Dan Kegel wrote: > It's a fact of life with valgrind that you will see > memory leaks from system libraries... you > just have to suppress them and move on. > If you're ambitious, you can make sure the > upstream project knows about the leak.
Many upstream devs will challenge you to say "does it only 'leak once'", i.e. create a re-usable structure with no obvious means to free it prior to termination? Or does it leak the same per iteration in some libc function? (i.e. ancient versions of strtok()) As an example, try reading /etc/passwd with what glibc (and most other POSIX systems) provide. In short, if you brought in foo.h .. and getfoo() leaks a static amount no matter how many times you call it .. you're dealing with a concession made in your C library (likely, to introduce re-entrant functions that accomplish the same and / or set errno, depending on the target kernel and distro). Cheers, --Tim -- Monkey + Typewriter = Echoreply ( http://echoreply.us ) ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) 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/devconference _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
