On Saturday 25 of October 2014, Timo Sirainen wrote:
On 25 Oct 2014, at 06:11, Arkadiusz Miśkiewicz arekm@maven.pl wrote:
fatal_printf_format_fix .............................................. : ok 0 / 190 tests failed ==6098== Invalid read of size 16 ==6098== at 0x317B880804: ??? (in /lib64/libc-2.20.so) ==6098== by 0x317B8A93B6: ??? (in /lib64/libc-2.20.so) ==6098== by 0x317B8AAA21: ??? (in /lib64/libc-2.20.so) ==6098== by 0x317B8A9C0F: ??? (in /lib64/libc-2.20.so) ==6098== by 0x317B8A9F94: ??? (in /lib64/libc-2.20.so) ==6098== by 0x42A0D7: utc_mktime (utc-mktime.c:39)
That's inside gmtime() call. Looks to me like a libc bug. What OS / libc / CPU is this with?
Anyway this code hasn't changed for years.
Ok, looks like that was valgrind fault.
linux, glibc 2.20, x86_64
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )