Message 188643 - Python tracker

➜

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.

In-reply-to
Author	pitrou
Recipients	benjamin.peterson, jsafrane, pitrou
Date	2013年05月07日.12:11:22
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1367928682.87.0.895891736685.issue17922@psf.upfronthosting.co.za>

Content
> 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 Ok. Still, you should be able to inspect the variables at the crash point. 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)? AFAICT, the only reason GET_WEAKREFS_LISTPTR() may crash is because of an invalid Py_TYPE(). Which should never happen.

Content

> 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
Ok. Still, you should be able to inspect the variables at the crash point. 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)?
AFAICT, the only reason GET_WEAKREFS_LISTPTR() may crash is because of an invalid Py_TYPE(). Which should never happen.

History
Date	User	Action	Args
2013年05月07日 12:11:22	pitrou	set	recipients: + pitrou, benjamin.peterson, jsafrane
2013年05月07日 12:11:22	pitrou	set	messageid: <1367928682.87.0.895891736685.issue17922@psf.upfronthosting.co.za>
2013年05月07日 12:11:22	pitrou	link	issue17922 messages
2013年05月07日 12:11:22	pitrou	create

homepage