GC question

Kerim Borchaev warkid at storm.ru
Thu Nov 8 20:53:51 CET 2001


Hello Neil.

Thursday, November 08, 2001, 10:18:46 PM, you wrote:
NS> The DEBUG_LEAK setting sets DEBUG_SAVEALL.  That means that all objects
NS> in unreachable cycles are added to gc.garbage.  If nested scopes are
NS> used reference cycles can easily be created (they are in your program).

you mean something like this: fun -> C -> C.m -> fun ?
But such depencies are resolved even without GC?

NS> Other than the fact that DEBUG_LEAK is badly named if you enable nested
NS> scopes, is there a problem?  What are you trying to achieve?

I'm trying to control memory leakage in my code.
I need to know which objects wasn't deallocated in proper moment.

Best regards,
 Kerim                            mailto:warkid at storm.ru






More information about the Python-list mailing list