Andreas Schwab wrote: > > FAIL: test-localtime_r > > ====================== > > > > test-localtime_r.c:58: assertion 'result->tm_hour == 18' failed > > FAIL test-localtime_r (exit status: 134) > > > > FAIL: test-localtime_r-mt > > ========================= > > > > thread2 disturbed by thread1! > > thread1 disturbed by thread2! > > FAIL test-localtime_r-mt (exit status: 134)
The second failure is a consequence of the first one. So, there is no MT-safety problem, "just" that localtime_r produces wrong results. I've seen this happen on OSes with a time zone database that is older than 5 or 10 years. Pádraig Brady wrote: > It may help to detail your platform. Yes. And make sure that it has a time zone database installed at all. Bruno
