From: Florian Weimer <fweimer@redhat.com>
To: Andreas Schwab <schwab@suse.de>
Cc: Joseph Myers <joseph@codesourcery.com>, libc-alpha@sourceware.org
Subject: Re: Pending fixes for all-ABIs builds
Date: Wed, 09 Nov 2016 13:39:00 -0000 [thread overview]
Message-ID: <0a922f13-5130-51ca-fc73-6c003dbb20ce@redhat.com> (raw)
In-Reply-To: <mvm8tssdbtf.fsf@hawking.suse.de>
On 11/09/2016 02:26 PM, Andreas Schwab wrote:
> On Nov 09 2016, Florian Weimer <fweimer@redhat.com> wrote:
>
>> On 11/09/2016 10:01 AM, Andreas Schwab wrote:
>>> On Nov 09 2016, Florian Weimer <fweimer@redhat.com> wrote:
>>>
>>>> Does this mean the dynamic linker starts with it's GOT pointer as NULL,
>>>> initializes that to point it to the malloc in elf/dl-minimal.c, and then,
>>>> once libc.so.6 is relocated updates its GOT pointer to point to the malloc
>>>> in libc.so.6?
>>>
>>> ld.so re-relocates itself after all static dependencies have been loaded
>>> and relocated.
>>
>> And even at this point, the code is used for future dynamic linking
>> operations?
>
> "The code" refers to what?
The code in ld.so.
Thanks,
Florian
next prev parent reply other threads:[~2016-11-09 13:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 23:25 Joseph Myers
2016-11-08 8:28 ` Florian Weimer
2016-11-08 23:22 ` Joseph Myers
2016-11-09 8:14 ` Florian Weimer
2016-11-09 8:18 ` Joseph Myers
2016-11-09 9:01 ` Andreas Schwab
2016-11-09 11:56 ` Florian Weimer
2016-11-09 13:26 ` Andreas Schwab
2016-11-09 13:39 ` Florian Weimer [this message]
2016-11-09 13:47 ` Andreas Schwab
2016-11-09 13:52 ` Florian Weimer
2016-11-09 14:50 ` Andreas Schwab
2016-11-09 14:54 ` Florian Weimer
2016-11-09 22:00 ` Roland McGrath
2016-11-10 7:58 ` Florian Weimer
2016-11-10 9:28 ` Andreas Schwab
2016-11-10 16:30 ` _rtld_global_ro and static dlopen (was: Re: Pending fixes for all-ABIs builds) Florian Weimer
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=0a922f13-5130-51ca-fc73-6c003dbb20ce@redhat.com \
--to=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).