[lxml-dev] is valgrind still used?

[Victor Ng]

Hi all,

It's been a long time since I've been on this list, but I'm hoping to start
hacking again.  Whoo!  New job.   More open source hacking time.  On to the
questions!

Is valgrind still being used anymore?  I just ran :

> valgrind --tool=memcheck --suppressions=valgrind-python.supp  python
test.py

and got:

==13242==
==13242== ERROR SUMMARY: 138 errors from 16 contexts (suppressed: 10026 from
6)
==13242== malloc/free: in use at exit: 2848232 bytes in 2981 blocks.
==13242== malloc/free: 53700 allocs, 50719 frees, 21000875 bytes allocated.
==13242== For counts of detected errors, rerun with: -v
==13242== searching for pointers to 2981 not-freed blocks.
==13242== checked 3490012 bytes.
==13242==
==13242== LEAK SUMMARY:
==13242==    definitely lost: 4759 bytes in 168 blocks.
==13242==      possibly lost: 0 bytes in 0 blocks.
==13242==    still reachable: 2843473 bytes in 2813 blocks.
==13242==         suppressed: 0 bytes in 0 blocks.
==13242== Use --leak-check=full to see details of leaked memory.
victorng at mbdev1:~/dev/lxml$

Is this expected? Is there a Trac instance or some other bug tracker that I
can look at to see what the open bugs are?

Thanks!  Hope to be less than useless soon.  :)

vic
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://codespeak.net/pipermail/lxml-dev/attachments/20060216/df262345/attachment-0001.htm