Jean-Paul Calderone <[EMAIL PROTECTED]> writes:
> Did you use the suppression file?
No, I didn't, because I was testing Valgrind on binaries that happened
to be installed on a Linux machine, and had no reason to treat Python
specifically. I see that README.valgrind explains why Python reads
memo
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
