[issue770280] PyMarshal_ReadLastObjectFromFile

Mark Dickinson added the comment: I think this is superseded by issue 7332, which is now fixed in trunk (but not in 2.6). -- nosy: +mark.dickinson, pitrou resolution: remind -> out of date status: open -> closed superseder: -> python script segment fault at PyMarshal_ReadLastObjectFro

[issue770280] PyMarshal_ReadLastObjectFromFile

Terry J. Reedy added the comment: Can this be closed as either out-of-date or rejected? -- nosy: +tjreedy status: pending -> open ___ Python tracker ___ ___

[issue770280] PyMarshal_ReadLastObjectFromFile

Paul Felix added the comment: Maybe not. With the addition of thread.stack_size([size]), it's fairly easy to get around the problem by bumping up the stack size. It would be nice if PyMarshal_ReadLastObjectFromFile didn't allocate a small file buffer on the stack (think of the impact when *recurs

[issue770280] PyMarshal_ReadLastObjectFromFile

Christian Heimes added the comment: Is the patch still interesting for Python 2.6? -- nosy: +tiran resolution: -> remind status: open -> pending versions: +Python 2.6 -Python 2.3 Tracker <[EMAIL PROTECTED]> _