Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Carlos O'Donell" <carlos@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>, libc-alpha@sourceware.org
Cc: gdb-patches@sourceware.org
Subject: Re: [libc patch] __tls_get_addr with link_map * instead of modid
Date: Fri, 24 Oct 2014 02:21:00 -0000	[thread overview]
Message-ID: <5449B78E.1060407@redhat.com> (raw)
In-Reply-To: <20141018201540.GA26252@host2.jankratochvil.net>

On 10/18/2014 04:15 PM, Jan Kratochvil wrote:
> Other option suggested by Tom Tromey is implemented by this patch:
> 
> * A new glibc function like __tls_get_addr that takes a link_map address
>   rather than a module id.

I do not think this is a good solution.

If you use this function in jit'd code, you've now deviated from what normal
TLS-accessing sequences look like. Now your code deviates from the published
tls.pdf in the call sequence, and is undocumented, though simple. On top of
that it's a stop-gap measure until we fix things correctly. Because of these
things I object to adding this function to ld's API.

I don't like libthread_db either, but it avoids us having to put a stop-gap
API in ld. I say stop-gap because the real solution is going to be to use
python/DWARF, not any API in ld.

I'm in favour of exactly 3 things:

* New function in libthread_db.

* Heuristics in gdb if libthread_db is not new enough.

* A python or DWARF based parser to replace libthread_db.

Cheers,
Carlos.


  parent reply	other threads:[~2014-10-24  2:21 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 [this message]
     [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=5449B78E.1060407@redhat.com \
    --to=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