]> granicus.if.org Git - python/commit
Allocating a new weakref object can cause existing weakref objects for
authorFred Drake <fdrake@acm.org>
Wed, 4 Feb 2004 23:14:14 +0000 (23:14 +0000)
committerFred Drake <fdrake@acm.org>
Wed, 4 Feb 2004 23:14:14 +0000 (23:14 +0000)
commitbc875f5a36b744c1a7263c35befaf31208a416b1
tree9b362880eeb66497bd813f43f2806eef2d2bb7f0
parent21ae4f983e3625cc16807c68952c6cd9fe44bb8b
Allocating a new weakref object can cause existing weakref objects for
the same object to be collected by the cyclic GC support if they are
only referenced by a cycle.  If the weakref being collected was one of
the weakrefs without callbacks, some local variables for the
constructor became invalid and have to be re-computed.

The test caused a segfault under a debug build without the fix applied.
Lib/test/test_weakref.py
Objects/weakrefobject.c