On 6/10/2004 7:02 PM, Ian Wienand wrote:
A guess : the only major difference with the optimised libraries is they enable __thread which has the effect of putting errno in the TLS area (sysdeps/unix/sysv/linux/i386). TLS uses the %gs register to get at the thread local data. Now for some reason the gs register gets trashed somewhere along the way, say in a signal handler, it's possible that you'd get a segfault? Anyone got any other ideas (cc: debian-glibc@lists.debian.org in case they do).
Sounds like a variant of this problem:
http://lia64.bkbits.net:8080/linux-ia64-2.5/[EMAIL PROTECTED]|src/|src/arch|src/arch/ia64|src/arch/ia64/ia32|related/arch/ia64/ia32/ia32_signal.c
Is it possible for you to make a tarball for this particular glibc available ? It doesn't fail for me with
# rpm -q glibc glibc-2.3.2-95.3
-Arun
