Message164849
>>> io.UnsupportedOperation.__new__(io.UnsupportedOperation)
behaves correctly now (rev d9c98730e2e8)
This bug was (I believe) caused somehow by an error in OSError_new() which did not initialize self->args if OSError_init() was not called.
Here is a crash which exploited the lack of initialization:
(Works on rev 2a142141e5fd)
>>> class C(ValueError, OSError):pass
...
>>> c = OSError.__new__(C)
>>> str(c)
Segmentation fault (core dumped)
This has already been fixed, so I'm closing this issue. |
|
Date |
User |
Action |
Args |
2012-07-07 14:03:22 | Mark.Shannon | set | recipients:
+ Mark.Shannon, ncoghlan, pitrou, larry, benjamin.peterson, tarek, eric.araujo, alexis |
2012-07-07 14:03:22 | Mark.Shannon | set | messageid: <1341669802.73.0.612072752068.issue14241@psf.upfronthosting.co.za> |
2012-07-07 14:03:22 | Mark.Shannon | link | issue14241 messages |
2012-07-07 14:03:22 | Mark.Shannon | create | |
|