unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniel Clemente <n142857@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 73022@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#73022: 31.0.50; Crash in build_frame_matrix_from_leaf_window after C-x 2 and reducing terminal size
Date: Sun, 8 Sep 2024 11:09:40 +0000	[thread overview]
Message-ID: <CAJKAhPDWJD-zbsomqr+BzxgP0hJH=vBnBPN74K0+0eN8xY6fzg@mail.gmail.com> (raw)
In-Reply-To: <60579ab6-db81-4f6e-b281-0cee03dc3b82@gmx.at>

> I attach the patch now, sorry for not doing it earlier.
>

Please attach patches if I can help trying out things. I don't know
this code so I may break it if I change the low-level behavior. But I
can safely add many breakpoints and debug messages to research the
bugs.
Apparently we could use more assertions in other parts of the code, or
move the existing ones (under glyph debug) to catch the problem
earlier.

In cmcheckmagic we have:
      if (!MagicWrap (tty) || curY (tty) >= FrameRows (tty) - 1)
          emacs_abort ();

Is this an assertion that needs to always hold? I have tried
copy-pasting it at the beginning of tty_write_glyphs and I found that
it fails continuously (e.g. it tests: 62 >= 63-1). Actually I used a
breakpoint instead of emacs_abort.
Are there useful places where I could trace that  the assertion holds
true?, earlier places than the current place.





  parent reply	other threads:[~2024-09-08 11:09 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-04  6:09 bug#73022: 31.0.50; Crash in build_frame_matrix_from_leaf_window after C-x 2 and reducing terminal size Daniel Clemente
     [not found] ` <handler.73022.B.172543028723315.ack@debbugs.gnu.org>
2024-09-04  6:25   ` bug#73022: Acknowledgement (31.0.50; Crash in build_frame_matrix_from_leaf_window after C-x 2 and reducing terminal size) Daniel Clemente
2024-09-04  7:28 ` bug#73022: 31.0.50; Crash in build_frame_matrix_from_leaf_window after C-x 2 and reducing terminal size martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-04 12:21   ` Eli Zaretskii
2024-09-04 13:23     ` Eli Zaretskii
2024-09-05  8:18       ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-05  9:19         ` Eli Zaretskii
2024-09-05 14:46           ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-05 14:58             ` Eli Zaretskii
2024-09-05 15:48               ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-05 16:05                 ` Eli Zaretskii
2024-09-05 16:30                   ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-05 16:58                     ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-05 18:41                       ` Eli Zaretskii
2024-09-05 18:15                     ` Eli Zaretskii
2024-09-08 11:07         ` Daniel Clemente
2024-09-08 14:36           ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-05  8:18     ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-05  9:18       ` Eli Zaretskii
2024-09-05 14:45         ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-05 15:10           ` Eli Zaretskii
2024-09-05 16:27             ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-08 11:08             ` Daniel Clemente
2024-09-08 11:31               ` Eli Zaretskii
2024-09-08 14:58               ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-10 17:43                 ` Daniel Clemente
2024-09-11  8:07                   ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-11 12:22                     ` Eli Zaretskii
2024-09-11 14:37                       ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-11 15:06                         ` Eli Zaretskii
2024-09-12  9:49                           ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-08 11:09       ` Daniel Clemente [this message]
2024-09-08 14:43         ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-08 15:32           ` Eli Zaretskii
2024-09-08 17:01             ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors

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='CAJKAhPDWJD-zbsomqr+BzxgP0hJH=vBnBPN74K0+0eN8xY6fzg@mail.gmail.com' \
    --to=n142857@gmail.com \
    --cc=73022@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=rudalics@gmx.at \
    /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).