From: "Óscar Fuentes" <oscarfv@telefonica.net>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: Pip Cet <pipcet@protonmail.com>, 74547@debbugs.gnu.org
Subject: bug#74547: 31.0.50; igc: assertion failed in buffer.c
Date: Sun, 01 Dec 2024 14:18:32 +0100 [thread overview]
Message-ID: <87r06rmthz.fsf@telefonica.net> (raw)
In-Reply-To: <m2plmbvbq4.fsf@gmail.com> ("Gerd Möllmann"'s message of "Sun, 01 Dec 2024 13:17:39 +0100")
Gerd Möllmann <gerd.moellmann@gmail.com> writes:
> Hm, reading Oscar's report again - he was using LSP. Maybe it's
> something in the parser.
The three times that I caugth the crash with the debugger mini-echo [1]
was in the Elisp backtrace. Maybe lsp-mode does something that upsets
the garbage collector and it surfaces when mini-echo executes. Just now
tried for some minutes with mini-echo active and without lsp-mode and no
crash, but maybe I was unlucky. lsp-mode is heavy on GC and it is
difficult to replicate that.
As for the core dump, I have two, but I'm not sure if they contain
sensitive info. Usually the crash takes a few minutes of work to happen.
I can execute Emacs under gdb on a controlled environment and then
answer your requests, no problem with having it open for several days.
Or send you the core dump, if it is more useful.
1. https://github.com/liuyinz/mini-echo.el
next prev parent reply other threads:[~2024-12-01 13:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 18:35 bug#74547: 31.0.50; igc: assertion failed in buffer.c Óscar Fuentes
2024-11-27 6:54 ` Gerd Möllmann
2024-12-01 10:49 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-01 12:05 ` Gerd Möllmann
2024-12-01 12:17 ` Gerd Möllmann
2024-12-01 12:30 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-01 12:39 ` Gerd Möllmann
2024-12-01 12:57 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-01 13:30 ` Gerd Möllmann
2024-12-01 14:58 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-01 15:18 ` Gerd Möllmann
2024-12-01 15:48 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-01 16:32 ` Geza Herman
2024-12-01 19:41 ` Gerd Möllmann
2024-12-01 21:15 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-04 19:11 ` Geza Herman
2024-12-01 15:55 ` Eli Zaretskii
2024-12-01 15:23 ` Eli Zaretskii
2024-12-01 15:30 ` Óscar Fuentes
2024-12-01 15:48 ` Gerd Möllmann
2024-12-01 15:58 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-01 16:24 ` Óscar Fuentes
2024-12-01 13:18 ` Óscar Fuentes [this message]
2024-12-01 13:44 ` Gerd Möllmann
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=87r06rmthz.fsf@telefonica.net \
--to=oscarfv@telefonica.net \
--cc=74547@debbugs.gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=pipcet@protonmail.com \
/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).