On Wed, Feb 11, 2009 at 3:13 PM, Gideon N. Guillen
<[email protected]> wrote:
> -original message-
> From: "Norbert P. Copones" <[email protected]>
> Date: 02/11/2009 13:54
>
>> 64-bit apps are not affected by this bug since they use 64-bit int on time_t.
>
> They're still affected for now because, AFAIK, most libc implementations,
> including x86-64
> version of Linux distros and Solaris SPARC, still are still "typedef long
> time_t" or "typedef
> long int time_t". In short, they are currently 32-bit on 64-bit platforms.
the only way to test this is to run this simple C code on different platforms...
#include <stdio.h>
#include <stdlib.h>
#include <time.h>
int main(void) {
printf("time_t = %d bits\n", sizeof(time_t) * 8);
return (0);
}
save it let say test.c, compile and run...
gcc -o test test.c
./test
normally, an application compiled in 64-bit operating system produced
a 64-bit time_t size... but a binary 32-bit application run on a
64-bit operating system with a backward compatibility to 32-bit
emulation produced a 32-bit time_t size...
fooler.
_________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
http://lists.linux.org.ph/mailman/listinfo/plug
Searchable Archives: http://archives.free.net.ph
