Running Python 2.5.1 under Valgrind is interesting; just starting it and then pressing Ctrl-D produces this:
==27082== ERROR SUMMARY: 713 errors from 56 contexts (suppressed: 10 from 1) ==27082== malloc/free: in use at exit: 1,243,153 bytes in 508 blocks. ==27082== malloc/free: 3,002 allocs, 2,494 frees, 2,748,487 bytes allocated. ==27082== For counts of detected errors, rerun with: -v ==27082== searching for pointers to 508 not-freed blocks. ==27082== checked 1,399,984 bytes. ==27082== ==27082== LEAK SUMMARY: ==27082== definitely lost: 0 bytes in 0 blocks. ==27082== possibly lost: 17,072 bytes in 58 blocks. ==27082== still reachable: 1,226,081 bytes in 450 blocks. ==27082== suppressed: 0 bytes in 0 blocks. ==27082== Reachable blocks (those to which a pointer was found) are not shown. ==27082== To see them, rerun with: --show-reachable=yes A lot of those 713 errors occur in the various deallocation functions. -- Esa Peuha student of mathematics at the University of Helsinki http://www.helsinki.fi/~peuha/ -- http://mail.python.org/mailman/listinfo/python-list
