➜

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 christian.heimes
Recipients Arfrever, christian.heimes, eli.bendersky, flox, georg.brandl, skrah
Date 2012-09-30.11:45:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1349005528.06.0.433995498573.issue16089@psf.upfronthosting.co.za>
In-reply-to
Content 
I can confirm that Stefan's fix works. I ran the SimpleTAL test suite about hundred times in a loop without a segfault. But I don't understand why the change fixes the issue. Could the alteration just lead to another code path so the erroneous code isn't triggered?

+1 for Py_CLEAR()
History
Date User Action Args
2012-09-30 11:45:28christian.heimessetrecipients: + christian.heimes, georg.brandl, Arfrever, eli.bendersky, skrah, flox
2012-09-30 11:45:28christian.heimessetmessageid: <1349005528.06.0.433995498573.issue16089@psf.upfronthosting.co.za>
2012-09-30 11:45:28christian.heimeslinkissue16089 messages
2012-09-30 11:45:27christian.heimescreate