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: Mon, 03 Jun 2024 19:03:53 +0300 [thread overview]
Message-ID: <86o78iko7q.fsf@gnu.org> (raw)
In-Reply-To: <CAJKAhPA2FuGMUsupSD8xi2+QwMttVGfrT-1SRAuafK0Morh85g@mail.gmail.com> (message from Daniel Clemente on Mon, 3 Jun 2024 15:56:17 +0000)
> From: Daniel Clemente <n142857@gmail.com>
> Date: Mon, 3 Jun 2024 15:56:17 +0000
> Cc: 71289@debbugs.gnu.org
>
> > Please investigate what happens with our SIGWINCH handler (in
> > dispnew.c) in these cases.
>
> In the case mentioned above, in which: after killing a frame and resizing another one, new sections appear
> black.
> I reported it as bug #71343, since it's not related to GC like this bug.
I'm not sure I understand: is this related to this bug in some way?
Bug#71343 seems to describe a GUI frame (if not, what does the
window-manager have to do with it?). While here we are talking about
TTY frames, right? And killing frames is not involved in this bug
report, right? Or what am I missing?
next prev parent reply other threads:[~2024-06-03 16:03 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 [this message]
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
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=86o78iko7q.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).