From: Florian Weimer <fw@deneb.enyo.de>
To: "Wendeborn\, Jonathan" <Jonathan.Wendeborn@bruker.com>
Cc: "Wendeborn\, Jonathan via Libc-help" <libc-help@sourceware.org>,
Konstantin Kharlamov <hi-angel@yandex.ru>
Subject: Re: AW: dlopen: Segfault due to overwriting .so file after it was loaded and loading it again
Date: Fri, 20 Nov 2020 13:48:51 +0100 [thread overview]
Message-ID: <874klkkxcc.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <c22f96ef84c54b1da2d2b8a6e416d5ad@bruexc101.brumgt.local> (Jonathan Wendeborn's message of "Fri, 20 Nov 2020 12:45:19 +0000")
* Jonathan Wendeborn:
> Thank you, that sounds reasonable. Indeed the library is marked
> NODELETE due to unique symbols. Is it forbidden in general to write
> executables which are loaded?
You need to follow a specific sequence: write the new version to a
temporary file, and after it has been written completely, rename that
version over the previous version. This way, the old file is not
truncated, and mapped versions of it continue to work.
It won't address the dependency on a unique symbol, though, that's
unrelated. It's not possible for now to unload such objects.
next prev parent reply other threads:[~2020-11-20 12:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 6:52 Wendeborn, Jonathan
2020-11-20 7:17 ` Konstantin Kharlamov
2020-11-20 8:01 ` AW: " Wendeborn, Jonathan
2020-11-20 8:15 ` Konstantin Kharlamov
2020-11-20 9:47 ` AW: " Wendeborn, Jonathan
2020-11-20 10:20 ` Konstantin Kharlamov
2020-11-20 11:33 ` Florian Weimer
2020-11-20 12:45 ` AW: " Wendeborn, Jonathan
2020-11-20 12:48 ` Florian Weimer [this message]
2020-11-20 12:59 ` AW: " Wendeborn, Jonathan
2020-12-04 10:39 Wendeborn, Jonathan
2020-12-04 10:44 ` AW: " Wendeborn, Jonathan
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=874klkkxcc.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=Jonathan.Wendeborn@bruker.com \
--cc=hi-angel@yandex.ru \
--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).