From: Eli Zaretskii <eliz@gnu.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: emacs-devel@gnu.org, silent2600@gmail.com, akrl@sdf.org
Subject: Re: changed dlopen flags in dynlib.c, gccemacs crash
Date: Sun, 06 Mar 2022 17:32:36 +0200 [thread overview]
Message-ID: <834k4bgkq3.fsf@gnu.org> (raw)
In-Reply-To: <CAArVCkSTpkoLvGHmf30FDCsVJDLF5=FP+LenCcMw-3dsTvinmA@mail.gmail.com> (message from Philipp Stephani on Sun, 6 Mar 2022 15:32:14 +0100)
> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Sun, 6 Mar 2022 15:32:14 +0100
> Cc: Eli Zaretskii <eliz@gnu.org>, hx <silent2600@gmail.com>,
> Emacs developers <emacs-devel@gnu.org>
>
> > yes, I think once we have verified the issue is what we suspect we could
> > dlopen eln files as before and have RTLD_GLOBAL added for the other
> > cases.
>
> This thread is already quite old, but let me point out that
> https://www.akkadia.org/drepper/dsohowto.pdf warns very strongly
> against using RTLD_GLOBAL (section 1.5.4), and I don't see a strong
> reason to not heed that warning. So I'd recommend removing RTLD_GLOBAL
> again.
We added it for a reason, and I don't see anything in Ulrich Drepper's
paper that could affect Emacs modules badly enough to back up on this.
That said, I don't see myself an expert on this stuff, so if enough
people here think it will have adverse effect on Emacs, I'm okay with
removing that flag, provided that we see some detailed explanations of
how this could be detrimental to use of Emacs modules.
prev parent reply other threads:[~2022-03-06 15:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 6:01 changed dlopen flags in dynlib.c, gccemacs crash hx
2021-12-08 13:15 ` Eli Zaretskii
2021-12-09 0:51 ` hx
2021-12-09 8:37 ` Eli Zaretskii
2021-12-09 10:53 ` Andrea Corallo
2021-12-09 12:08 ` Eli Zaretskii
2021-12-09 20:47 ` Andrea Corallo
2021-12-11 2:29 ` hx
2021-12-11 8:23 ` Eli Zaretskii
2021-12-11 18:09 ` Andrea Corallo
2021-12-11 18:23 ` Eli Zaretskii
2021-12-11 20:53 ` Andrea Corallo
2021-12-15 15:26 ` Andrea Corallo
2021-12-15 16:59 ` Eli Zaretskii
2022-03-06 14:32 ` Philipp Stephani
2022-03-06 15:32 ` Eli Zaretskii [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834k4bgkq3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=akrl@sdf.org \
--cc=emacs-devel@gnu.org \
--cc=p.stephani2@gmail.com \
--cc=silent2600@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).