➜

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.10:50:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1367923835.33.0.365068001702.issue17922@psf.upfronthosting.co.za>
In-reply-to
Content 
> First, have you seen the following message on that bug report:
> http://bugs.python.org/issue16602#msg177180

I'm reading it now... I searched for PyWeakref_GET_OBJECT in cmpi-bindings and both occurrences generated by SWIG and both look safe.
Is it hidden/wrapped by any other macro?

Sorry, I don't know much about python internals and extension development, I'm not author of cmpi-bindings.

And I'm attaching stack trace with --with-pydebug. Debugging with gdb is quite a problem, I have gdb linked with distribution Python 2.7.4 and it doesn't cooperate with my custom built python, which I have in LD_LIBRARY_PATH (so Pegasus gets the right one when loading providers).
History
Date User Action Args
2013-05-07 10:50:36jsafranesetrecipients: + jsafrane, pitrou, benjamin.peterson
2013-05-07 10:50:35jsafranesetmessageid: <1367923835.33.0.365068001702.issue17922@psf.upfronthosting.co.za>
2013-05-07 10:50:35jsafranelinkissue17922 messages
2013-05-07 10:50:35jsafranecreate