Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "John Bates" <johnnybates@gmail.com>
To: gdb@sourceware.org
Subject: Re: thread local storage (__thread) variables aren't working in gdb 6.5/6.6?
Date: Mon, 25 Jun 2007 23:20:00 -0000	[thread overview]
Message-ID: <a4c7fade0706251620j7b526855r87b374c257fbd7d0@mail.gmail.com> (raw)
In-Reply-To: <a4c7fade0706191322o513a3860r88ce81f2f0384b83@mail.gmail.com>

It would be helpful to update the GDB man/info/docs to state that
thread local storage is not supported. It would also help to print an
error when attempting to access TLS __thread variable that says
"thread local storage is not supported." Currently, GDB implies that
__thread variables are bad addresses--for example, "Cannot access
memory at address 0x0". I have verified the same result in GDB 6.4,
6.5 and 6.6, with and without libpthread linked with the ELF. A simple
test case is in the email below if anyone is interested in checking
this.

Best regards,
John


On 6/19/07, John Bates <johnnybates@gmail.com> wrote:
> I can't find any confirmation of support or non-support of thread
> local storage on the web or in the gdb documentation. I already tried
> 6.6 and it was the same problem. The test below seems to confirm
> non-support on my fedora core 6 (kernel 2.6.18) x86 distribution with
> gdb 6.5. Please let me know if I am doing something wrong for
> debugging __thread global variables.
>
> Thanks,
> John
>
>
> --- begin main.cpp ---
> __thread int tlstest = 5;
>
> int main()
> {
>         tlstest = 4; // line 5
>         return 0;
> }
>
> --- begin Makefile ---
> CXXFLAGS += -g
> main : main.o
>
> jbates@localhost:~/samples/tls_test$ make
> g++ -g   -c -o main.o main.cpp
> cc   main.o   -o main
> jbates@localhost:~/samples/tls_test$ gdb main
> GNU gdb Red Hat Linux (6.5-15.fc6rh)
> Copyright (C) 2006 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "i386-redhat-linux-gnu"...Using host
> libthread_db library "/lib/libthread_db.so.1".
>
> (gdb) b main.cpp:5
> Breakpoint 1 at 0x8048352: file main.cpp, line 5.
> (gdb) run
> Starting program: /home/jbates/samples/tls_test/main
>
> Breakpoint 1, main () at main.cpp:5
> 5               tlstest = 4;
> (gdb) p tlstest
> Cannot access memory at address 0x0
> (gdb)
>


  parent reply	other threads:[~2007-06-25 23:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-19 20:22 John Bates
2007-06-19 20:28 ` Daniel Jacobowitz
2007-06-19 20:56   ` John Bates
2007-06-19 21:04     ` Daniel Jacobowitz
2007-06-25 23:20 ` John Bates [this message]
2007-06-26 17:06   ` Jim Blandy
2007-06-26 18:48     ` John Bates
2007-06-26 23:52       ` Jim Blandy
2009-04-09 18:48       ` ajitnayak
     [not found]         ` <20090409200657.GA22217@host0.dyn.jankratochvil.net>
     [not found]           ` <b1bfafd50904130735x32d369a0ub4005758d7d9e2c8@mail.gmail.com>
2009-04-13 19:00             ` Jan Kratochvil

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a4c7fade0706251620j7b526855r87b374c257fbd7d0@mail.gmail.com \
    --to=johnnybates@gmail.com \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox