unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <akrl@sdf.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 51688@debbugs.gnu.org, schwab@linux-m68k.org
Subject: bug#51688: ELC+ELN  international/emoji.elc crashes
Date: Tue, 23 Nov 2021 15:29:40 +0000	[thread overview]
Message-ID: <xjfsfvm3n6j.fsf@ma.sdf.org> (raw)
In-Reply-To: <871r36j4om.fsf@gmail.com> (Robert Pluim's message of "Tue, 23 Nov 2021 16:02:33 +0100")

Robert Pluim <rpluim@gmail.com> writes:

>>>>>> On Tue, 23 Nov 2021 14:46:55 +0000, Andrea Corallo <akrl@sdf.org> said:
>
>     Andrea> $ gcc emoji-aca2d225-0997194d_libgccjit_repro.c -lgccjit
>     >> 
>     Andrea> And run it to see if it crashes.
>     >> 
>     Andrea> $ ./a.out
>     >> 
>     >> No, that doesnʼt crash. And similarly for the .c files in
>     >> .emacs.d/eln-cache, they donʼt crash.
>
>     Andrea> To be sure, was the .c file produced when Emacs crashed?
>
> Not quite, it was produced when I reran the compile but with the
> comp-libgccjit-reproducer set to t. The crash doesnʼt always happen
> the second time.

It's really important we make sure the reproducer is produced when Emacs
crashes.  Could you clean-up the old repro before each test so we make
sure we get a new repro that we know is correlated with the crashy run?

> But I have a live emacs process thatʼs just crashed (the first time)
> trapped in gdb if you want me to poke at it.

I think without libgccjit with debug symbols there's not much that can be
easily inferred here.

BTW which libgccjit version are you on? (looks farily recent)

Thanks

  Andrea





  reply	other threads:[~2021-11-23 15:29 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 [this message]
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=xjfsfvm3n6j.fsf@ma.sdf.org \
    --to=akrl@sdf.org \
    --cc=51688@debbugs.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 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).