From: Eli Zaretskii <eliz@gnu.org>
To: Michael Lausch <mick.lausch@gmail.com>
Cc: 70342@debbugs.gnu.org
Subject: bug#70342: 29.3.50; treesitter and RTLD_GLOBAL
Date: Thu, 11 Apr 2024 21:54:39 +0300 [thread overview]
Message-ID: <86il0nu3v4.fsf@gnu.org> (raw)
In-Reply-To: <CAMDrkBcmBPiaZ8i1e4__Va2KQEf_vQCYnssD7FFyqoMW1yt2Yg@mail.gmail.com> (message from Michael Lausch on Thu, 11 Apr 2024 20:47:50 +0200)
> From: Michael Lausch <mick.lausch@gmail.com>
> Date: Thu, 11 Apr 2024 20:47:50 +0200
> Cc: 70342@debbugs.gnu.org
>
> > A solution can be:
> > 1) use a special call to dlopen without the RTLD_OPEN flag, sim,ilar to what the eln loader does.
> > 2) fix all the grammars and make all functions 'static' so that the functions are not visible outside the
> > compilation unit.
> > 3) something i didn't think about
>
> If those 'serialize' functions are not needed to be called from
> outside of the shared library, the usual way is not to export them,
> i.e. to give all symbols except the few that need to be exported the
> so-called "hidden visibility".
>
> I agree that this would be the cleanest way to solve the problem, but that would mean to patch all the existing
> grammars and maybe all the future grammars and push the changes to their maintainers.
>
> I started to prep patches for the yaml and org grammar (those were the ones which triggered the bug for me)
> and i'm going to have them merged upstream.
I understand, but why is this an Emacs problem? We use RTLD_GLOBAL
for a reason, and the problem of not exposing unnecessary symbols
should be solved by the respective libraries and those who build them.
next prev parent reply other threads:[~2024-04-11 18:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 17:38 bug#70342: 29.3.50; treesitter and RTLD_GLOBAL Michael Lausch
2024-04-11 18:39 ` Eli Zaretskii
2024-04-11 18:47 ` Michael Lausch
2024-04-11 18:54 ` Eli Zaretskii [this message]
2024-04-11 19:04 ` Michael Lausch
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=86il0nu3v4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=70342@debbugs.gnu.org \
--cc=mick.lausch@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.