From: Elena Zannoni <ezannoni@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: ezannoni@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA/RFC] thread local storage tests
Date: Sat, 08 Feb 2003 04:35:00 -0000 [thread overview]
Message-ID: <15940.35318.229578.586185@localhost.redhat.com> (raw)
In-Reply-To: <200302080039.h180d4C22676@duracef.shout.net>
Michael Elizabeth Chastain writes:
> http://www.shout.net/~mec/sunday/2003-02-07-tls/index.html
>
> These tests use '__thread' which is available with gcc gcc-3_3-branch
> and later. So if you want to work on the test themselves you need
> to grab a 3.3 or 3.4 compiler.
>
> They also have problems even with those compilers.
>
> Michael C
thanks, this is really useful.
Hmm, I suspected that. I was able to get them to run in the current
Redhat rawhide.
What glibc(s) were you using? It may also be due to slightly versions
of binutils, even though, you are also using HEAD binutils, and it
should work there.
I don't know whether stabs has support for TLS, I doubt it. In
dwarf2, if you use readelf -w, you should see, for the thread local
variables, a DW_OP_GNU_tls_push_address, in the debug info.
I ran into a compiler version that compiled the file happily, but
didn't produce the right information, It was marking the variale as a
regular static one.
On my system it refuses to compile it, I get the 2 unsupported
tests. At least something matches. :-(
Do you have the gdb.logs for the cases that almost work?
Elena
next prev parent reply other threads:[~2003-02-08 4:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-08 1:32 Michael Elizabeth Chastain
2003-02-08 4:35 ` Elena Zannoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-08 5:41 Michael Elizabeth Chastain
2003-02-08 16:50 ` Elena Zannoni
2003-02-08 0:04 Elena Zannoni
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=15940.35318.229578.586185@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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