From: Andrea Corallo <akrl@sdf.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: silent2600@gmail.com, emacs-devel@gnu.org
Subject: Re: changed dlopen flags in dynlib.c, gccemacs crash
Date: Wed, 15 Dec 2021 15:26:20 +0000 [thread overview]
Message-ID: <xjfczlxsxcz.fsf@ma.sdf.org> (raw)
In-Reply-To: <xjftufesw1o.fsf@ma.sdf.org> (Andrea Corallo's message of "Sat, 11 Dec 2021 20:53:23 +0000")
Andrea Corallo <akrl@sdf.org> writes:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: Andrea Corallo <akrl@sdf.org>
>>> Cc: hx <silent2600@gmail.com>, emacs-devel@gnu.org
>>> Date: Sat, 11 Dec 2021 18:09:56 +0000
>>>
>>> > So at this point, I think this bug report should be treated as
>>> > "wishlist", i.e. a feature request: to support RTLD_GLOBAL in dynlib
>>> > with native-comp. Andrea, is that feasible, and if so, what would it
>>> > entail?
>>>
>>> Hi Eli,
>>>
>>> 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.
>>>
>>> I'll have a look into next week and report on the feature request.
>>
>> Thanks. One (unchecked) idea is to use 2 different versions of
>> dynlib_open: one for loading *.eln files, the other for every other
>> kind of dynamic loading.
>
> Agree, 2 different versions of dynlib_open was my idea as well.
Hi all,
I've implemented the mentioned idea of having two different
'dynlib_open' and pushed that as e6b93245fe. Contextually I've added
the RTLD_GLOBAL flag to 'dlopen'.
Note the Windows version of the new 'dynlib_open' is just a wrapper to
the old one as I don't know if something has to be done there or not
(nor I know how to test it).
BR
Andrea
next prev parent reply other threads:[~2021-12-15 15:26 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 [this message]
2021-12-15 16:59 ` Eli Zaretskii
2022-03-06 14:32 ` Philipp Stephani
2022-03-06 15:32 ` Eli Zaretskii
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=xjfczlxsxcz.fsf@ma.sdf.org \
--to=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--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).