* Should libstdc++ (and libgcc_s) be NODELETE?
@ 2019-12-02 14:20 Florian Weimer
0 siblings, 0 replies; only message in thread
From: Florian Weimer @ 2019-12-02 14:20 UTC (permalink / raw)
To: libstdc++; +Cc: gcc
libstdc++ recently made an appearance in a glibc bug, which made me
realize that they aren't marked as NODELETE (on GNU ELF platforms).
(The bug in question was purely glibc, though.)
Are these shared objects really expected to be unloaded? Given that
libstdc++ contains many destructors, I expect that unloading will be
problematic in most cases. Unloading libgcc_s also seems a bit over the
top to me.
This only matters if any of the shared objects is loaded late via
dlopen. If the main program is linked against them, they are implicitly
NODELETE anyway.
Thoughts? Should these shared objects be linked with -z nodelete?
Thanks,
Florian
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-12-02 14:20 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-12-02 14:20 Should libstdc++ (and libgcc_s) be NODELETE? Florian Weimer
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).