➜

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 steve.dower
Recipients BreamoreBoy, JohnLeitch, belopolsky, brycedarling, eryksun, larry, lemburg, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2015-09-05.19:18:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1441480687.87.0.507924568588.issue24917@psf.upfronthosting.co.za>
In-reply-to
Content 
> Rather than debating about how various platforms handle malformed 
> format strings for strftime(), and whether or not they crash, we 
> should simply prevent the native strftime() function from seeing 
> them in the first place.

The crash is nothing to do with the native strftime() function - Python was crashing because it *tried* to prevent malformed strings and we (I) got it wrong. If we were simply passing the string through unchecked this would not have been an issue (or it would have been an issue against the CRT).

PR at https://bitbucket.org/larry/cpython350/pull-requests/18/issue-24917-time_strftime-buffer-over-read/diff
History
Date User Action Args
2015-09-05 19:18:07steve.dowersetrecipients: + steve.dower, lemburg, paul.moore, belopolsky, vstinner, larry, tim.golden, BreamoreBoy, zach.ware, eryksun, JohnLeitch, brycedarling
2015-09-05 19:18:07steve.dowersetmessageid: <1441480687.87.0.507924568588.issue24917@psf.upfronthosting.co.za>
2015-09-05 19:18:07steve.dowerlinkissue24917 messages
2015-09-05 19:18:07steve.dowercreate