From: Jan Engelhardt <jengelh@xxxxxxxxxx> Date: Mon, 14 Dec 2009 15:22:16 +0100 (CET) > I added some dump_stack() to all the cp_* functions, leading > to this result: > > Call Trace: > [0000000000522990] cp_new_stat+0xdc/0x134 > [0000000000522d9c] SyS_newfstat+0x24/0x38 > [0000000000406294] linux_sparc_syscall+0x34/0x44 > > Is glibc doing the right thing here? Calling sys_newfstat (instead of > sys_newfstat64) for fstat64()? That's completely bogus. And I can't reproduce your problem on debian unstable. What are you using, Fedora? Maybe something is fubared in their glibc build or the checkout they are using. davem@sunset:~/src/GIT/linux-2.6$ /lib/libc.so.6 --version GNU C Library (EGLIBC) stable release version 2.10.2, by Roland McGrath et al. ... davem@sunset:~/src/GIT/linux-2.6$ gcc -m64 -o x x.c davem@sunset:~/src/GIT/linux-2.6$ ./x 1260862562.0 1260862562.0 1260862562.0 davem@sunset:~/src/GIT/linux-2.6$ I even checked current glibc GIT and everything looks kosher there too. -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
