Message147413
It is definitely a glibc issue. Here's a C snippet to reproduce:
"""
#include <time.h>
#include <stdlib.h>
int main() {
time_t t;
struct tm tmp;
char str[200];
t = time(NULL);
tmp = *gmtime(&t);
tmp.tm_gmtoff = 0;
tmp.tm_zone = NULL;
strftime(str, sizeof(str), "%Z", &tmp);
puts(str);
t = -2461446500;
localtime(&t);
t = time(NULL);
tmp = *gmtime(&t);
tmp.tm_gmtoff = 0;
tmp.tm_zone = NULL;
strftime(str, sizeof(str), "%Z", &tmp);
puts(str);
return 0;
}
"""
Output:
CET
PMT
Calling localtime() or mktime() with a time largely in the past seems to corrupt the glibc's internal time structures (the "char *tm_zone[]"). |
|
Date |
User |
Action |
Args |
2011-11-10 23:38:14 | pitrou | set | recipients:
+ pitrou, vinay.sajip, belopolsky, nadeem.vawda, Arfrever, flox, rosslagerwall, python-dev |
2011-11-10 23:38:14 | pitrou | set | messageid: <1320968294.41.0.481853718841.issue13309@psf.upfronthosting.co.za> |
2011-11-10 23:38:13 | pitrou | link | issue13309 messages |
2011-11-10 23:38:13 | pitrou | create | |
|