From: joakim@verona.se
To: Eli Zaretskii <eliz@gnu.org>
Cc: 54814@debbugs.gnu.org, Andrea Corallo <akrl@sdf.org>
Subject: bug#54814: 29.0.50; symbol visibility in modules may cause emacs crash in nativ-compilation emacs
Date: Sat, 09 Apr 2022 18:18:10 +0200 [thread overview]
Message-ID: <877d7yqlh9.fsf@tanaka.verona.se> (raw)
In-Reply-To: <83h7728hy3.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 09 Apr 2022 17:11:48 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: joakim@verona.se
>> Date: Sat, 09 Apr 2022 15:09:48 +0200
>>
>>
>> symbol visibility in modules may cause emacs crash in nativ-compilation
>> emacs
>
> Does it really have to do anything with native-compilation? The fixes
> seem to be to compile the external modules with less visibility, but
> that doesn't affect Emacs, only the modules.
>
> Or am I missing something?
Well, I'm not really sure, but I have a couple of different builds of
emacs, and when I load the emacs-zmq precompiled binaries they crash my
main emacs, which has native-compilation, but not the other emacs I
tried this in. I also get the same result of crashing native emacs, when
using the packaged build proceedure of emacs-zmq. The hidden-visibility
branch seems to fix these problems.
Can I help pinpointing the issue somehow?
>
>
>
--
Joakim Verona
joakim@verona.se
next prev parent reply other threads:[~2022-04-09 16:18 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 [this message]
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
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=877d7yqlh9.fsf@tanaka.verona.se \
--to=joakim@verona.se \
--cc=54814@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
/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.