public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Harley Paterson via Libc-alpha <libc-alpha@sourceware.org>
Cc: Harley Paterson <harley.paterson@postgrad.otago.ac.nz>
Subject: Re: Dynamic Linker: Exposing static symbols at runtime
Date: Thu, 22 Oct 2020 09:57:22 +0200	[thread overview]
Message-ID: <87o8kusnfh.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <SYAPR01MB2639C6994AB3DA68AFCFA3629D1D0@SYAPR01MB2639.ausprd01.prod.outlook.com> (Harley Paterson via Libc-alpha's message of "Thu, 22 Oct 2020 05:23:38 +0000")

* Harley Paterson via Libc-alpha:

> I'm doing some research on dynamic software updating recently. I've
> found it would be very helpful to expose static symbols to running
> program, much like `dlopen`, `dlsym`, and friends expose dynamic
> symbols to running programs via the `dlfcn.h` header.
>
> Is anyone able to provide insight into what work is required to get
> the `ld-linux.so` to read the static symbol stable, and expose symbols
> to processes via an API?

In general, the static symbol table is not mapped into memory because it
is not located in an allocated section.  So the dynamic loader cannot
provide this data any more easily than a separate library could: it
would have to load it from disk as a first step, too.  This suggests to
me that glibc integration is not really needed.

Thanks,
Florian
-- 
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill


      reply	other threads:[~2020-10-22  7:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-22  5:23 Harley Paterson
2020-10-22  7:57 ` Florian Weimer [this message]

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=87o8kusnfh.fsf@oldenburg2.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=harley.paterson@postgrad.otago.ac.nz \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).