Re: [Fwd: memory leaks in python interface [was Hash view questions]]

 Ralf Schmitt wrote:

> Using a debug build of python (i.e. configure --with-pydebug), one
> notices a massive amount references not being decref'ed. I'll have a 
> look at it.

Ralf: Great!

Please keep us informed.

By the way, the valgrind results that I posted were with current SVN head of
Python built with pydebug on.  valgrind is an excellent tool, and if you are
working on Linux then I recommend that you spend a couple of minutes learning
how to use it.


Basically you just prepend the command "valgrind" before your executable name
on the command-line, and then add the following options if you want:

--leak-check=full --leak-resolution=high --show-reachable=yes

Regards,

Zooko

P.S.  The full valgrind command-line that I used looked like this:

rm v.* ; time valgrind --suppressions=/home/zooko/glibc2.3.5-dynload.supp --suppressions=/home/zooko/python.supp --suppressions=/usr/lib/valgrind/glibc-2.3.supp --log-file=v --leak-check=full --leak-resolution=high --show-reachable=yes /usr/local/bin/python -OO ./leakcheck.py

P.P.S.  /home/zooko/glibc2.3.5-dynload.supp and /home/zooko/python.supp
available on request, but perhaps unnecessary if your Linux distribution has
already provided good .supp files.
_____________________________________________
Metakit mailing list  -  [email protected]
http://www.equi4.com/mailman/listinfo/metakit