unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <akrl@sdf.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 51688@debbugs.gnu.org
Subject: bug#51688: ELC+ELN  international/emoji.elc crashes
Date: Wed, 17 Nov 2021 16:27:44 +0000	[thread overview]
Message-ID: <xjfv90q4uin.fsf@ma.sdf.org> (raw)
In-Reply-To: <87tugazt49.fsf@igel.home> (Andreas Schwab's message of "Wed, 17 Nov 2021 16:42:14 +0100")

Andreas Schwab <schwab@linux-m68k.org> writes:

> On Nov 17 2021, Andrea Corallo wrote:
>
>> Andreas Schwab <schwab@linux-m68k.org> writes:
>>
>>> On Nov 17 2021, Andrea Corallo wrote:
>>>
>>>> If the crash is on the libgccjit side IMO it indicates it's a libgccjit
>>>> bug.
>>>
>>> It can easily be a wrong use of it, too.
>>
>> Agree, but it should not crash.
>
> If you pass it invalid data (like use-after-free), it may not be able to
> avoid a crash.

That is true.  OTOH the API of libgccjit AFAIK is made to copy any
region of memory passed to it during the libgccjit record phase so it's
quite robust in this sense.

Here we are crashing calling from 'comp_compile_ctxt_to_file' therfore
we are in the replay phase and use-after-free should have caused a
problem earlier.

I can't prove my conclusion is correct, but that's what my knowledge and
experience on this system tells me here.

Anyway, if someone has access to a machine were we can reproduce it,
creating a libgccjit reproducer using `comp-libgccjit-reproducer' should
be the way to look at it and test if my idea is correct or not.

Regards

  Andrea





  reply	other threads:[~2021-11-17 16:27 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 [this message]
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
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

  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=xjfv90q4uin.fsf@ma.sdf.org \
    --to=akrl@sdf.org \
    --cc=51688@debbugs.gnu.org \
    --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 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).