From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Jakob Skaar <jakobrs100@gmail.com>
Cc: libc-help@sourceware.org
Subject: Re: [Feature Request] dlopen_from function
Date: Wed, 23 Jun 2021 08:37:52 +0100 [thread overview]
Message-ID: <20210623073751.GE13058@arm.com> (raw)
In-Reply-To: <CAO+Dw49vJeUt8KSOwjK6Tv5BfLRfuVpawWYriMruwpTArhg=bg@mail.gmail.com>
The 06/19/2021 09:23, Jakob Skaar via Libc-help wrote:
> Hi,
>
> The behaviour of certain functions in libdl[^2] like the `dlopen`
> function is dependent on where it is called from. This is normally
> what you want, but sometimes you may want to specify the caller
> address yourself, for example when intercepting/hooking the `dlopen`
> function itself. For this reason, Apple has added the `dlopen_from`
> function in macOS Big Sur. `dlopen_from` has an extra parameter, `void
> *caller`, that specifies the "fake" caller address to be used instead
> of `RETURN_ADDRESS(0)`[^3]. Using `dlopen_from` significantly
> simplifies intercepting `dlopen` calls (see [here][1] for an example).
> So my feature request is to implement `dlopen_from` in glibc too.
i think glibc specific feature requests should go to
bugzilla.
but i would be useful to discuss this on
libc-coord@lists.openwall.com to see if there is
interest across implementations otherwise the api
will not work portably.
>
> [1]: <https://github.com/clementgallet/libTAS/blob/70966f9e1f400dfdd5176bba63c11cb6026d3da6/src/library/dlhook.cpp#L108-L189>
> [^2]: The same logic also applies to `dlmopen`, `dlsym`, and `dlvsym`.
> [^3]: Header file where `dlopen_from` is declared:
> <https://opensource.apple.com/source/dyld/dyld-832.7.3/include/dlfcn_private.h.auto.html>
next prev parent reply other threads:[~2021-06-23 7:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-19 7:23 Jakob Skaar
2021-06-23 7:37 ` Szabolcs Nagy [this message]
2021-06-23 12:12 ` Jakob Skaar
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=20210623073751.GE13058@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=jakobrs100@gmail.com \
--cc=libc-help@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).