A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2002-February/020220.html below:

[Python-Dev] A little GC confusion

[Python-Dev] A little GC confusion [Python-Dev] A little GC confusionDavid Abrahams David Abrahams" <david.abrahams@rcn.com
Thu, 21 Feb 2002 09:42:34 -0500
----- Original Message -----
From: "Thomas Heller" <thomas.heller@ion-tof.com>


> From: "David Abrahams" <david.abrahams@rcn.com>
> > Hi All,
> >
> > The following extension module (AA) is a reduced example of what I'm
doing
> > to make extension
> > classes in 2.2. I followed the examples given by typeobject.c. When I
> > "import AA,pdb" I get a crash in GC.
>
> For me it crashes after
>   import AA, gc
>   gc.collect()
> (Win2k Prof, SP1, MSVC6.0)
>
> I'm not really sure, but it seems your code does not crash any longer
> if you remove the Py_TPFLAGS_HAVE_GC from your definition of
class_metatype_object.

Yes, I'm aware of that. What I don't understand is how  the builtin metatype
gets away with Py_TPFLAGS_HAVE_GC when some of its instance types are not
even heap-allocated.

-Dave




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