From: Eli Zaretskii <eliz@gnu.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: 54814@debbugs.gnu.org, joakim@verona.se
Subject: bug#54814: 29.0.50; symbol visibility in modules may cause emacs crash in nativ-compilation emacs
Date: Mon, 11 Apr 2022 14:20:14 +0300 [thread overview]
Message-ID: <831qy37tox.fsf@gnu.org> (raw)
In-Reply-To: <xjfa6cs9fjr.fsf@ma.sdf.org> (message from Andrea Corallo on Mon, 11 Apr 2022 08:42:48 +0000)
> From: Andrea Corallo <akrl@sdf.org>
> Cc: joakim@verona.se, 54814@debbugs.gnu.org
> Date: Mon, 11 Apr 2022 08:42:48 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> The crash does happen inside the module, but for me, only in native
> >> compilation emacs.
> >
> > Andrea, any ideas how native-compilation could have triggered these
> > crashes?
>
> Not at the moment, so far I'm of your same opinion that this is not
> strictly related to native compilation but accidentally triggered by it.
Thanks.
I guess the next step is to ask someone who has access to that module
to show a list of exported symbols before and after the change which
made the crash go away, while still using Emacs with
native-compilation. Then we might have some ideas by comparing these
two lists of exported symbols.
prev parent reply other threads:[~2022-04-11 11:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-09 13:09 bug#54814: 29.0.50; symbol visibility in modules may cause emacs crash in nativ-compilation emacs joakim
2022-04-09 14:11 ` Eli Zaretskii
2022-04-09 16:18 ` joakim
2022-04-09 16:23 ` Eli Zaretskii
2022-04-09 18:30 ` joakim
2022-04-10 8:33 ` Eli Zaretskii
2022-04-11 8:42 ` Andrea Corallo
2022-04-11 11:20 ` 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=831qy37tox.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=54814@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=joakim@verona.se \
/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).