On Mon, 20 May 2019 17:07:59 +
Szabolcs Nagy wrote:
> and the R_*_TLSIE_* relocs are for .LANCHOR3 + 0,
> so there will be one GOT entry for the 3 objects
> and you should see
That may indeed explain what is going on. I'll
have to take a closer look at the specific
ubuntu libraries I have
On 20/05/2019 16:59, Tom Horsley wrote:
> On Mon, 20 May 2019 15:43:53 +
> Szabolcs Nagy wrote:
>
>> you can verify that 0x152000 + 3608 == 0x152e18 is
>> indeed a GOT entry (falls into .got) and there is a
>>
>> 00152e18 R_AARCH64_TLS_TPREL64 *ABS*+0x0010
>
> There are
On Mon, 20 May 2019 15:43:53 +
Szabolcs Nagy wrote:
> you can verify that 0x152000 + 3608 == 0x152e18 is
> indeed a GOT entry (falls into .got) and there is a
>
> 00152e18 R_AARCH64_TLS_TPREL64 *ABS*+0x0010
There are a couple of other TLS variables in malloc, and I
On 17/05/2019 14:51, Tom Horsley wrote:
> I'm trying (for reason too complex to go into) to
> locate the TLS offset of the tcache_shutting_down
> variable from malloc in the ubuntu provided
> glibc on aarch64 ubuntu 18.04.
>
> Various "normal" TLS variables appear to operate
> much like x86_64
On 5/17/19 2:51 PM, Tom Horsley wrote:
> I'm trying (for reason too complex to go into) to
> locate the TLS offset of the tcache_shutting_down
> variable from malloc in the ubuntu provided
> glibc on aarch64 ubuntu 18.04.
>
> Various "normal" TLS variables appear to operate
> much like x86_64
I'm trying (for reason too complex to go into) to
locate the TLS offset of the tcache_shutting_down
variable from malloc in the ubuntu provided
glibc on aarch64 ubuntu 18.04.
Various "normal" TLS variables appear to operate
much like x86_64 with a GOT table entry where the
TLS offset of the
