From: Simon Marchi <simark@simark.ca>
To: Florian Weimer <fweimer@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: Getting offset of inital-exec TLS variables on GNU/Linux
Date: Thu, 23 May 2019 15:55:00 -0000 [thread overview]
Message-ID: <c693fcb5-7e87-014d-1cc4-f1b207cb5b67@simark.ca> (raw)
In-Reply-To: <87a7flp2tm.fsf@oldenburg2.str.redhat.com>
On 2019-05-17 10:34 a.m., Florian Weimer wrote:
> * Simon Marchi:
>
>> On 2019-05-17 6:21 a.m., Florian Weimer wrote:
>>> Is it possible to obtain the offset of initial-exec TLS variable on
>>> GNU/Linux?
>>>
>>> It doesn't seem so because GDB executes the DWARF to access the TLS
>>> variable, so the offset is an implementation detail. Although it is
>>> often visible at the ELF layer.
>>>
>>> Thanks,
>>> Florian
>>
>> Can you clarify a little bit?
>>
>> You are looking for the offset the variable from which point of reference:
>>
>> - The start of the TLS area of this module?
>> - The start of the TLS area of the current thread?
>
> The offset from something related to the thread pointer to the variable,
> for cases where this is constant (specifically, initial-exec TLS
> variables).
>
>> Also, are you looking for something you can find statically, with just the
>> executable, or are you working in the context of the live process?
>
> I have a live process, and it would be best if the information matched
> that process (even if it uses different libraries than those currently
> installed in the file system).
Hi Florian,
I am still a bit unsure of what you are looking for concretely. Are you looking for
a GDB command to print this offset? Do you need to compute the offset in an external
tool? what information are you starting with? I think that a bit more context would
help us help you.
GDB uses libthread_db to get the location of TLS variables, which leaves all
implementation details about this to glibc. And since you are a glibc maintainer, I
am not too sure what I can teach you about this, as you probably know more about this
than I do.
Simon
next prev parent reply other threads:[~2019-05-23 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87o941pej8.fsf@oldenburg2.str.redhat.com>
2019-05-17 14:34 ` Simon Marchi
2019-05-19 13:00 ` Florian Weimer
2019-05-23 15:55 ` Simon Marchi [this message]
2019-05-24 19:32 ` Florian Weimer
2019-05-24 20:12 ` Carlos O'Donell
2019-05-25 0:45 ` Florian Weimer
2019-05-25 22:35 ` Carlos O'Donell
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=c693fcb5-7e87-014d-1cc4-f1b207cb5b67@simark.ca \
--to=simark@simark.ca \
--cc=fweimer@redhat.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