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 bernie9998
Recipients barry, belopolsky, bernie9998, mark.dickinson, r.david.murray
Date 2010-09-17.21:31:56
SpamBayes Score 7.0285404e-09
Marked as misclassified No
Message-id <1284759117.95.0.331779490259.issue9888@psf.upfronthosting.co.za>
In-reply-to
Content
After further investigation, it appears the cause is the ability to overflow the datetime object by almost a year.  I've modified the test to demonstrate this relative to the current date:

from datetime import date, datetime, timedelta
(datetime.now()-timedelta((date.today()-date(1,1,1)).days+364)).ctime()

It seems the date can be overflowed by up to a year without throwing an Exception.  The result of which is a seg fault when calling the bound ctime method.

Note that anything above 364 results in OverFlowError.  Below 18 still overflows, but does not seg fault, instead resulting in a weird result,e.g.:
'Tue (null) 240 17:25:37 0001'

I'll update the script to demonstrate the edge cases where this occurs.
History
Date User Action Args
2010-09-17 21:31:58bernie9998setrecipients: + bernie9998, barry, mark.dickinson, belopolsky, r.david.murray
2010-09-17 21:31:57bernie9998setmessageid: <1284759117.95.0.331779490259.issue9888@psf.upfronthosting.co.za>
2010-09-17 21:31:56bernie9998linkissue9888 messages
2010-09-17 21:31:56bernie9998create