From: Florian Weimer <fweimer@redhat.com>
To: "Александр Ващилко via Libc-help" <libc-help@sourceware.org>
Cc: "Александр Ващилко" <alexander.armoken@gmail.com>
Subject: Re: dlmopen and isolation of loaded libraries
Date: Mon, 27 Feb 2023 14:10:51 +0100 [thread overview]
Message-ID: <87v8jnmexw.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAJ6FTedRHzMa+zcrOgeYom0=eGi3jvjkuSfLMtitpV0AwwaB=Q@mail.gmail.com> (=?utf-8?B?ItCQ0LvQtdC60YHQsNC90LTRgCDQktCw0YnQuNC70LrQvg==?= via Libc-help"'s message of "Mon, 27 Feb 2023 11:48:05 +0000")
* Александр Ващилко via Libc-help:
> Anyway, even if dlmopen doesn't support the required functionality, do
> glibc and libstdc++ support the simultaneous existence of different
> versions of these libraries at the same time in the same process?
For glibc, there can only be one version, and it has to match the build
of ld.so. Even with an identical libc.so.6 everywhere, there is some
loss of functionality (e.g., the secondary namespaces cannot create
threads).
For libstdc++, it may work depending on what you are doing and how
different the versions are. Even with dlmopen, STB_GNU_UNIQUE symbols
lack full isolation. Like the stdio streams, std::cout etc. will not
work reliably because the required global data is not shared across
instances. It's also not possible in general to pass pointers from one
namespace to the other even if the types are the same.
Thanks,
Florian
next prev parent reply other threads:[~2023-02-27 13:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 11:48 Александр Ващилко
2023-02-27 13:10 ` Florian Weimer [this message]
2023-02-27 16:57 ` Basile Starynkevitch
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=87v8jnmexw.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=alexander.armoken@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).