From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Clemente <n142857@gmail.com>
Cc: 71289@debbugs.gnu.org
Subject: bug#71289: 30.0.50; cmcheckmagic aborts when tty_write_glyphs writes "Garbage collecting..." in some cases
Date: Thu, 06 Jun 2024 10:55:36 +0300 [thread overview]
Message-ID: <86bk4eijyf.fsf@gnu.org> (raw)
In-Reply-To: <CAJKAhPDtzfT-ivabzWTgnnem1Bj5+eydO1J9pr+yYNuHw3dfoQ@mail.gmail.com> (message from Daniel Clemente on Wed, 5 Jun 2024 13:51:43 +0000)
> From: Daniel Clemente <n142857@gmail.com>
> Date: Wed, 5 Jun 2024 13:51:43 +0000
> Cc: 71289@debbugs.gnu.org
>
> > > I also saw a new type of TTY+GC error (not sure if it's the same issue
> > > as this bug):
> > >
> > > alloc.c:7517: Emacs fatal error: assertion failed: t->name != NULL
> > >
> > > Breakpoint 1, terminate_due_to_signal (sig=6,
> > > backtrace_limit=2147483647) at emacs.c:443
> > > 443 signal (sig, SIG_DFL);
> > > (gdb) bt
> > > #0 terminate_due_to_signal (sig=6, backtrace_limit=2147483647) at emacs.c:443
> > > #1 0x000055555573591a in die (msg=0x55555586f838 "t->name != NULL",
> > > file=0x55555586e97e "alloc.c", line=7517) at alloc.c:8082
> > > #2 0x00005555557346e8 in mark_terminals () at alloc.c:7517
> >
> > If this was while you only resized the terminal, how come a terminal
> > was deleted? Any idea what would cause this?
>
> I assume that it's t->name == NULL what tells you that a terminal was deleted.
Yes.
> But apparently this terminal wasn't fully deleted, because it's in the
> terminal_list. If delete_terminal had run, shouldn't it have removed
> it from the list?
It should have, yes.
> So I don't know what happened. reference_count is still 1.
What's more important, kboard, keyboard_coding, and terminal_coding
are not NULL. Which means delete_terminal_internal was never run for
this terminal. I don't understand how that could happen, given the
backtrace you show.
I found some unsafe code in delete_terminal and installed a fix. I
cannot explain how that code could have caused the assertion violation
inside mark_terminals, but maybe it did.
next prev parent reply other threads:[~2024-06-06 7:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 10:18 bug#71289: 30.0.50; cmcheckmagic aborts when tty_write_glyphs writes "Garbage collecting..." in some cases Daniel Clemente
2024-05-31 11:17 ` Eli Zaretskii
2024-05-31 17:07 ` Daniel Clemente
2024-05-31 18:17 ` Eli Zaretskii
2024-06-03 15:35 ` Daniel Clemente
2024-06-03 16:21 ` Eli Zaretskii
2024-05-31 17:09 ` Daniel Clemente
2024-05-31 18:26 ` Eli Zaretskii
2024-06-03 15:56 ` Daniel Clemente
2024-06-03 16:03 ` Eli Zaretskii
2024-06-03 16:28 ` Daniel Clemente
2024-06-03 16:36 ` Eli Zaretskii
2024-06-03 16:51 ` Daniel Clemente
2024-06-03 17:44 ` Eli Zaretskii
2024-06-05 13:51 ` Daniel Clemente
2024-06-06 7:55 ` Eli Zaretskii [this message]
2024-06-03 15:36 ` Daniel Clemente
2024-06-03 16:25 ` Eli Zaretskii
2024-06-03 16:55 ` Daniel Clemente
2024-06-03 17:39 ` Eli Zaretskii
2024-06-05 13:50 ` Daniel Clemente
2024-06-05 15:06 ` Eli Zaretskii
2024-06-05 16:43 ` Eli Zaretskii
2024-06-06 12:36 ` Daniel Clemente
2024-06-06 12:34 ` Daniel Clemente
2024-06-06 14:53 ` Eli Zaretskii
2024-06-06 15:23 ` Daniel Clemente
2024-06-06 16:13 ` Eli Zaretskii
2024-06-06 16:44 ` Daniel Clemente
2024-06-06 18:06 ` Daniel Clemente
2024-06-07 6:11 ` Eli Zaretskii
2024-06-07 6:42 ` Daniel Clemente
2024-06-07 6:47 ` Eli Zaretskii
2024-06-05 13:52 ` Daniel Clemente
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=86bk4eijyf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71289@debbugs.gnu.org \
--cc=n142857@gmail.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).