[Python-Dev] Valgrind on 2.2.2

[Guido van Rossum]

>   Just been lurkin' :) Possibly lost means that Valgrind didn't see
> any freeing for a specific point after a malloc. In valgrind terms,
> you probably forgot to free a pointer and lost all points that could
> reference that memory. In other words, a leak :) Usually 75% of those
> errors can be solved locally within the function, although I haven't
> looked at the specifics, but that 25% can get nasty.

Booh.

That statistic doesn't apply to Python -- there are no "simple" leaks
left in Python's C code, the remaining ones are all nasty.

Also, valgrind carefully distinguishes between "definitely lost" and
"possibly lost".  What's the difference?

--Guido van Rossum (home page: http://www.python.org/~guido/)