[issue15229] stringification of subclasses of OSError can cause crash

Antoine Pitrou added the comment: It should be fixed now. -- resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker ___ ___

[issue15229] stringification of subclasses of OSError can cause crash

Roundup Robot added the comment: New changeset 1cbab581bf1e by Antoine Pitrou in branch 'default': Issue #15229: An OSError subclass whose __init__ doesn't call back http://hg.python.org/cpython/rev/1cbab581bf1e -- nosy: +python-dev ___ Python tracke

[issue15229] stringification of subclasses of OSError can cause crash

Antoine Pitrou added the comment: Here is a quick patch (needs a test): diff --git a/Objects/exceptions.c b/Objects/exceptions.c --- a/Objects/exceptions.c +++ b/Objects/exceptions.c @@ -834,6 +834,7 @@ oserror_init(PyOSErrorObject *self, PyOb #endif /* Steals the reference to args */ +

[issue15229] stringification of subclasses of OSError can cause crash

Changes by Antoine Pitrou : -- nosy: +pitrou priority: normal -> high ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue15229] stringification of subclasses of OSError can cause crash

New submission from Richard Oudkerk : If you subclass OSError without calling OSError.__init__() then you can get a crash. For example Python 3.3.0b1 (default:cfbe51e66749, Jun 30 2012, 20:50:54) [MSC v.1600 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for m