From: Alexandre Oliva <aoliva@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: libc-alpha@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [libc patch] __tls_get_addr with link_map * instead of modid
Date: Thu, 23 Oct 2014 10:03:00 -0000 [thread overview]
Message-ID: <ork33rw1c5.fsf@free.home> (raw)
In-Reply-To: <20141018201540.GA26252@host2.jankratochvil.net> (Jan Kratochvil's message of "Sat, 18 Oct 2014 22:15:40 +0200")
On Oct 18, 2014, Jan Kratochvil <jan.kratochvil@redhat.com> wrote:
> * A new glibc function like __tls_get_addr that takes a link_map address
> rather than a module id.
dlinfo offers operations to both map a link_map (AKA dlopen handle) to
the modid, and to get the TLS base address for that link_map. I suppose
calling dlinfo directly is not an option, since there's no guarantee
that libdl will have been linked in.
However, the implementat of dlinfo RTLD_DI_TLS_DATA relies on
_dl_tls_get_addr_soft, that not only takes a struct link_map*, but also
refrains from assigning a TLS segment for the module in the running
thread when one isn't allocated already. I think this would be
preferrable behavior for a debugger, to avoid heisenbugs.
This symbol is not exported by ld.so, but this shouldn't stop GDB from
using it, since it is present in the symbol table as a local (hidden)
symbol.
--
Alexandre Oliva, freedom fighter http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/ FSF Latin America board member
Free Software Evangelist|Red Hat Brasil GNU Toolchain Engineer
next prev parent reply other threads:[~2014-10-23 10:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-18 20:15 Jan Kratochvil
2014-10-18 21:20 ` Rich Felker
2014-10-18 21:27 ` Jan Kratochvil
2014-10-18 21:44 ` Rich Felker
2014-10-23 10:03 ` Alexandre Oliva [this message]
2014-10-23 12:52 ` Jan Kratochvil
2014-10-24 1:47 ` Mike Frysinger
2014-10-24 2:21 ` Carlos O'Donell
[not found] ` <20141024093834.GA24090@host2.jankratochvil.net>
2014-10-24 14:22 ` Carlos O'Donell
2014-10-24 14:40 ` Jan Kratochvil
2014-10-24 15:00 ` Carlos O'Donell
2014-10-25 5:55 ` Rich Felker
2014-10-25 6:14 ` Jan Kratochvil
2014-10-25 6:26 ` Rich Felker
2014-10-24 15:56 ` Pedro Alves
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=ork33rw1c5.fsf@free.home \
--to=aoliva@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=libc-alpha@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