➜

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 belopolsky
Recipients Trundle, amaury.forgeotdarc, belopolsky, benjamin.peterson, brian.curtin, db3l, georg.brandl, pitrou, vstinner
Date 2011-01-03.16:56:35
SpamBayes Score 4.6629367e-15
Marked as misclassified No
Message-id <AANLkTikCARnmubmw1akHkN9ctpGGQysg9nD874c=UsJT@mail.gmail.com>
In-reply-to <1294073020.04.0.983571805286.issue10814@psf.upfronthosting.co.za>
Content 
On Mon, Jan 3, 2011 at 11:43 AM, Brian Curtin <report@bugs.python.org> wrote:
..
> No crash on 0-day or 300,000. I bumped it up to 3,000,000 and got a UnicodeDecodeError, although
> I'm not sure of the relevance of that to this issue.

It looks like we need an XP box with a debug version of the crt lib to
reproduce the crash.

..
>>>> time.asctime((3000000, 1, 0, 0, 0, 0, 0, 0, 0))
> Traceback (most recent call last):
>  File "<stdin>", line 1, in <module>
> UnicodeDecodeError: 'utf8' codec can't decode byte 0xe8 in position 20: invalid continuation byte

Well, undefined behavior is undefined behavior.  Arguably, writing
binary garbage in a timestamp is better than crashing.  (given Windows
reputation, I would not be surprised if the above also involves
undetected memory corruption, though.) I am convinced that we don't
have a choice but to check the input of asctime() beforehand.  I am
preparing a patch.
History
Date User Action Args
2011-01-03 16:56:36belopolskysetrecipients: + belopolsky, georg.brandl, db3l, amaury.forgeotdarc, pitrou, vstinner, benjamin.peterson, Trundle, brian.curtin
2011-01-03 16:56:35belopolskylinkissue10814 messages
2011-01-03 16:56:35belopolskycreate