This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Pending fixes for all-ABIs builds


On 11/09/2016 02:47 PM, Andreas Schwab wrote:
On Nov 09 2016, Florian Weimer <fweimer@redhat.com> wrote:

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.

If that's the only one.

Does this mean that if the application links against -ldl and invokes dlopen, a different dynamic linker implementation is used? And the ld.so implementation is only used for internal dynamic loading, e.g. for NSS modules or gconv modules?

Thanks,
Florian


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]