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.
-- Mike
On Thu, Oct 17 @ 20:38, Guido van Rossum wrote:
> There are a few other records mentioning GC_Resize, but this one is
> the biggest. Could it be that the free frame list is botched? OTOH,
> what does "possibly lost" really mean?
--
Michael Gilfix
mgilfix@eecs.tufts.edu
For my gpg public key:
http://www.eecs.tufts.edu/~mgilfix/contact.html
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4