This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: thread local storage (__thread) variables aren't working in gdb 6.5/6.6?
- From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: ajit nayak <nayakajit at gmail dot com>
- Cc: gdb at sourceware dot org, John Bates <johnnybates at gmail dot com>
- Date: Mon, 13 Apr 2009 18:08:53 +0200
- Subject: Re: thread local storage (__thread) variables aren't working in gdb 6.5/6.6?
- References: <a4c7fade0706191322o513a3860r88ce81f2f0384b83@mail.gmail.com> <a4c7fade0706251620j7b526855r87b374c257fbd7d0@mail.gmail.com> <m3tzsuhci3.fsf@codesourcery.com> <a4c7fade0706261148n4cc3fa21j563bec9c1841c480@mail.gmail.com> <22974723.post@talk.nabble.com> <20090409200657.GA22217@host0.dyn.jankratochvil.net> <b1bfafd50904130735x32d369a0ub4005758d7d9e2c8@mail.gmail.com>
Hi Ajit,
[ http://sourceware.org/bugzilla/show_bug.cgi?id=9384 ]
On Mon, 13 Apr 2009 16:35:30 +0200, ajit nayak wrote:
[snip]
> Below are the details. I did try with gdb-6.8 (after compining both with
> g++), but no luck..ran into the same problem.
if you try CVS HEAD it should work:
cvs -d :pserver:anoncvs@sourceware.org:/cvs/src co gdb
> However if I compile with gcc with a ".c" file (NOT .cpp) extension (gcc -g
> tls.cpp -o tls -lpthread), everyting works fine, i can access teh thread
> local variable from gdb. But my requirement is to compile .cpp files with
> g++ .
Checked the difference, both g++-4.3 and gcc-4.1 use more simple format as
read by `readelf -wi':
<1><88>: Abbrev Number: 7 (DW_TAG_variable)
<89> DW_AT_name : i
[snip]
<91> DW_AT_external : 1
<92> DW_AT_location : 10 byte block: 3 0 0 0 0 0 0 0 0 e0 (DW_OP_addr: 0; DW_OP_GNU_push_tls_address or DW_OP_HP_unknown)
while g++-4.1 uses:
<2><d2>: Abbrev Number: 7 (DW_TAG_variable)
DW_AT_name : i
[snip]
DW_AT_external : 1
DW_AT_declaration : 1
<1><de>: Abbrev Number: 8 (DW_TAG_variable)
DW_AT_specification: <d2>
DW_AT_location : 10 byte block: 3 0 0 0 0 0 0 0 0 e0 (DW_OP_addr: 0; DW_OP_GNU_push_tls_address)
Which is perfectly valid DWARF but current GDB cannot cope with it.
It starts working in post-6.8 FSF GDB because it gets resolved as an external
TLS reference. External TLS references did not work before. It is not
completely correct but in practice it works. Fixed by this patch:
http://sourceware.org/ml/gdb/2008-07/threads.html#00341
http://sourceware.org/ml/gdb-patches/2008-08/threads.html#00026
http://sourceware.org/ml/gdb-patches/2008-09/threads.html#00204
http://sourceware.org/ml/gdb-patches/2008-11/threads.html#00706
http://sourceware.org/ml/gdb-patches/2008-12/threads.html#00003
http://sourceware.org/ml/gdb-cvs/2008-12/msg00009.html
> [nz@TT4-A022 thread]$ cat /etc/redhat-release
> Red Hat Enterprise Linux Server release 5.2 (Tikanga)
> *[nz@TT4-A022 thread]$ g++ -g tls.cpp -o tls -lpthread*
=> Also using g++43 (bare g++ is 4.1 on RHEL-5.2) would workaround GDB.
HTH,
Jan