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 LambertDW, amaury.forgeotdarc, barry, christian.heimes, vstinner
Date 2008-10-30.14:15:51
SpamBayes Score 5.037526e-12
Marked as misclassified No
Message-id <1225376155.21.0.858698372464.issue4237@psf.upfronthosting.co.za>
In-reply-to
Content
The new patch fixes the problem and adds a unit test, too.

The bug was caused by a design flaw -- which was partly my fault. Some
elements of the PyFileIOObject struct were initialized in __new__ while
other parts were initialized in __init__. I've moved the initialization
to __new__.

We should add a rule that all struct members must be properly
initialized in __new__. In the past Victor's fuzzying tool has revealed
several crashers related to similar design flaws.

I'm raising the severity of the bug to release blocker because I can't
predict if the problem can be abused to crash the interpreter. We should
also review all __new__ and __init__ methods of objects and extension
modules for similar issues.
History
Date User Action Args
2008-10-30 14:15:55christian.heimessetrecipients: + christian.heimes, barry, amaury.forgeotdarc, vstinner, LambertDW
2008-10-30 14:15:55christian.heimessetmessageid: <1225376155.21.0.858698372464.issue4237@psf.upfronthosting.co.za>
2008-10-30 14:15:54christian.heimeslinkissue4237 messages
2008-10-30 14:15:52christian.heimescreate