From: "Martin Liška" <mliska@suse.cz>
To: Andrea Corallo <akrl@sdf.org>, Eli Zaretskii <eliz@gnu.org>
Cc: rpluim@gmail.com, 51688@debbugs.gnu.org,
Andreas Schwab <schwab@linux-m68k.org>
Subject: bug#51688: ELC+ELN international/emoji.elc crashes
Date: Wed, 24 Nov 2021 16:23:53 +0100 [thread overview]
Message-ID: <c66db0a1-a193-59de-5ea8-7eaecc8f31c6@suse.cz> (raw)
In-Reply-To: <xjffsrl37ss.fsf@ma.sdf.org>
On 11/24/21 16:14, Andrea Corallo wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: Andreas Schwab <schwab@linux-m68k.org>
>>> Cc: rpluim@gmail.com, akrl@sdf.org, 51688@debbugs.gnu.org
>>> Date: Wed, 24 Nov 2021 14:06:04 +0100
>>>
>>> On Nov 24 2021, Eli Zaretskii wrote:
>>>
>>>> Do you happen to know which libgccjit versions are affected by the
>>>> bug? We could tell people to avoid them.
>>>
>>> Most likely all of them.
>>
>> Too bad.
>>
>> Andrea, can anything be done to work around this somehow (except to
>> upgrade to a later GCC)? Or is there nothing we can do except keep
>> fingers crossed?
>
> I don't think there's much we can do to work around this on Emacs side
> (Martin please correct me if I'm wrong).
No, it's UBSAN in libgccjit library. Unfortunately, the issue is there
for quite a long time and it was exposed by a bad luck where an used
memory was reused (and not initialized) in libgccjit.
Martin
>
>>>> Or did this bug exist since day one? (But if it's an old bug, why
>>>> doesn't everyone see these crashes?)
>>>
>>> That's the effect of undefined behaviour.
>>
>> You mean, undefined behavior in libgccjit's own code, right? Or in
>> our code?
>
> In libgccjit's own code.
>
> BR
>
> Andrea
>
next prev parent reply other threads:[~2021-11-24 15:23 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 13:11 bug#51688: ELC+ELN international/emoji.elc crashes Andreas Schwab
2021-11-08 13:41 ` Eli Zaretskii
2021-11-08 13:50 ` Andreas Schwab
2021-11-08 14:04 ` Eli Zaretskii
2021-11-08 13:45 ` Lars Ingebrigtsen
2021-11-08 14:46 ` Andreas Schwab
2021-11-08 15:39 ` Lars Ingebrigtsen
2021-11-17 15:30 ` Andrea Corallo
2021-11-17 15:34 ` Andreas Schwab
2021-11-17 15:40 ` Andrea Corallo
2021-11-17 15:42 ` Andreas Schwab
2021-11-17 16:27 ` Andrea Corallo
2021-11-17 16:35 ` Andreas Schwab
2021-11-18 9:02 ` Andrea Corallo
2021-11-18 9:12 ` Andreas Schwab
2021-11-18 9:21 ` Andrea Corallo
2021-11-22 10:51 ` Andreas Schwab
2021-11-22 14:48 ` Eli Zaretskii
2021-11-22 14:55 ` Robert Pluim
2021-11-23 8:44 ` Robert Pluim
2021-11-23 12:42 ` Eli Zaretskii
2021-11-23 13:18 ` Robert Pluim
2021-11-23 14:03 ` Robert Pluim
2021-11-23 14:11 ` Eli Zaretskii
2021-11-23 14:15 ` Robert Pluim
2021-11-23 14:27 ` Eli Zaretskii
2021-11-23 14:34 ` Andrea Corallo
2021-11-23 14:42 ` Robert Pluim
2021-11-23 14:46 ` Andrea Corallo
2021-11-23 15:02 ` Robert Pluim
2021-11-23 15:29 ` Andrea Corallo
2021-11-23 16:00 ` Robert Pluim
2021-11-24 9:39 ` Andreas Schwab
2021-11-24 13:00 ` Eli Zaretskii
2021-11-24 13:06 ` Andreas Schwab
2021-11-24 13:18 ` Eli Zaretskii
2021-11-24 15:14 ` Andrea Corallo
2021-11-24 15:23 ` Martin Liška [this message]
2021-11-25 10:57 ` Andrea Corallo
2021-11-25 11:17 ` Eli Zaretskii
2021-11-23 11:22 ` Andreas Schwab
2021-11-23 11:36 ` Andreas Schwab
2021-11-23 12:56 ` Eli Zaretskii
2021-11-23 13:10 ` Eli Zaretskii
2021-11-23 13:22 ` Robert Pluim
2021-11-23 14:29 ` Andrea Corallo
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=c66db0a1-a193-59de-5ea8-7eaecc8f31c6@suse.cz \
--to=mliska@suse.cz \
--cc=51688@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=rpluim@gmail.com \
--cc=schwab@linux-m68k.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.