This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jsafrane
Recipients benjamin.peterson, jsafrane, pitrou
Date 2013-05-07.14:09:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1367935744.99.0.720767274392.issue17922@psf.upfronthosting.co.za>
In-reply-to
Content
> Could you try to inspect the `self` variable inside weakref_dealloc,
> especially `self->wr_object` and its Py_TYPE() value? Also, what is the
> value of Py_REFCNT(self->wr_object)?

in weakref_dealloc at Objects/weakrefobject.c:106:

(gdb) p *self
$1 = {_ob_next = 0x0, _ob_prev = 0x0, ob_refcnt = 0, ob_type = 0x7fdb8ffc91a0 <_PyWeakref_RefType>}

(gdb) p *((PyWeakReference*)self)
$7 = {_ob_next = 0x0, _ob_prev = 0x0, ob_refcnt = 0, ob_type = 0x7fdb8ffc91a0 <_PyWeakref_RefType>, wr_object = 0x7fdb9c30bc00 <swigpyobject_type.9541>, wr_callback = 0x0, hash = -1, 
  wr_prev = 0x0, wr_next = 0x0}

(gdb) p *((PyWeakReference*)self)->wr_object
$9 = {_ob_next = 0x0, _ob_prev = 0x0, ob_refcnt = 0, ob_type = 0x0}

If I am reading Py_TYPE right, Py_TYPE(self->wr_object) must be 0 (=NULL).

<swigpyobject_type.9541> seems to be PyTypeObject generated by SWIG in cmpi-bindings, I'll dig into it. Please let me know if there is anything suspicious or worth checking.
History
Date User Action Args
2013-05-07 14:09:05jsafranesetrecipients: + jsafrane, pitrou, benjamin.peterson
2013-05-07 14:09:04jsafranesetmessageid: <1367935744.99.0.720767274392.issue17922@psf.upfronthosting.co.za>
2013-05-07 14:09:04jsafranelinkissue17922 messages
2013-05-07 14:09:04jsafranecreate