Hi, 
I've been struggling the last few days on getting gdb
to work correctly on a powerpc64 machine. Built as
ppc-64-linux, debugging ppc64 binaries linked against
libpthread. It seems to me that gdb's TLS access does
not work correctly on these platforms. Attempting to
print a variable of type __thread doesnt work. 

Here's a paste:

shadows:~/pniyogi # ldd ./tls
        linux-vdso64.so.1 =>  (0x0000000000100000)
        libpthread.so.0 => /lib64/libpthread.so.0 
        libgcc_s.so.1 => /lib64/libgcc_s.so.1 
        libc.so.6 => /lib64/libc.so.6 
        /lib64/ld64.so.1 (0x0000040000000000)
shadows:~/pniyogi # ./gdb-new ./tls
GNU gdb 6.5.50.20060811-cvs
***********
(gdb) b 80
Breakpoint 1 at 0x10000d6c: file tls.c, line 80.
(gdb) r
Starting program: /root/pniyogi/tls
[New LWP 8210]
[Switching to LWP 8210]

Breakpoint 1, spin (vp=0x0) at tls.c:80
80          thread_local_val[ me ] = a_thread_local; 
(gdb) p a_thread_local
Cannot find thread-local variables on this target
(gdb)

Also attaching a testcase tls.c that I was compiling
with -m64 -g 

Any assistance/insight would be appreciated. 

-Prosun Niyogi

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com