From: Eli Zaretskii <eliz@gnu.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: silent2600@gmail.com, emacs-devel@gnu.org
Subject: Re: changed dlopen flags in dynlib.c, gccemacs crash
Date: Thu, 09 Dec 2021 14:08:58 +0200 [thread overview]
Message-ID: <834k7iugit.fsf@gnu.org> (raw)
In-Reply-To: <xjf5yryujzu.fsf@ma.sdf.org> (message from Andrea Corallo on Thu, 09 Dec 2021 10:53:57 +0000)
> From: Andrea Corallo <akrl@sdf.org>
> Cc: hx <silent2600@gmail.com>, emacs-devel@gnu.org
> Date: Thu, 09 Dec 2021 10:53:57 +0000
>
> > Andrea, any better ideas? I don't understand the reason for the
> > crash, as we seem to have defenses against this in Fnative_elisp_load,
> > so I'm probably missing something.
>
> Hello all,
>
> I'm no expert on 'dlopen' so I'm not sure about the impact of using
> RTLD_GLOBAL. But should be noted that .eln files do share a number of
> symbol names, I'm wondering if this could be somehow problematic when
> using RTLD_GLOBAL, that's my suspect here.
Assuming the RTLD_GLOBAL flag was added.
But still, the crash is because we assume a Lisp object is a cons cell
and take its CDR. So evidently it isn't a cons cell (probably nil),
and I don't understand how that could be caused, not even if
RTLD_GLOBAL was used.
next prev parent reply other threads:[~2021-12-09 12:08 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 [this message]
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
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=834k7iugit.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=akrl@sdf.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).