Message75370
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. |
|
Date |
User |
Action |
Args |
2008-10-30 14:15:55 | christian.heimes | set | recipients:
+ christian.heimes, barry, amaury.forgeotdarc, vstinner, LambertDW |
2008-10-30 14:15:55 | christian.heimes | set | messageid: <1225376155.21.0.858698372464.issue4237@psf.upfronthosting.co.za> |
2008-10-30 14:15:54 | christian.heimes | link | issue4237 messages |
2008-10-30 14:15:52 | christian.heimes | create | |
|