From: Rich Felker <dalias@libc.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Carlos O'Donell <carlos@redhat.com>,
libc-alpha@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [libc patch] __tls_get_addr with link_map * instead of modid
Date: Sat, 25 Oct 2014 05:55:00 -0000 [thread overview]
Message-ID: <20141025055516.GJ22465@brightrain.aerifal.cx> (raw)
In-Reply-To: <20141024144014.GA2193@host2.jankratochvil.net>
On Fri, Oct 24, 2014 at 04:40:14PM +0200, Jan Kratochvil wrote:
> On Fri, 24 Oct 2014 16:22:29 +0200, Carlos O'Donell wrote:
> > What's wrong with using libthread_db to get the module ID and then you can
> > call the normal TLS functions
> +
> > Isn't a solution to use libthread_db to get the module ID from the link_map,
> > then use that with normal __tls_get_addr instead of adding to ld's API?
>
> I forgot about this possibility - that libthread_db would provide just the
> module ID (and not some per-thread address).
Why not just use dl_iterate_phdr to get the module id?
Rich
next prev parent reply other threads:[~2014-10-25 5:55 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
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 [this message]
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=20141025055516.GJ22465@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=carlos@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