From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 60096@debbugs.gnu.org, juri@linkov.net
Subject: bug#60096: 29.0.60; Crash in format_mode_line_unwind_data
Date: Sat, 17 Dec 2022 10:17:00 +0100 [thread overview]
Message-ID: <325aaa94-74fa-cf94-b66c-b87c69ebe386@gmx.at> (raw)
In-Reply-To: <83fsdfjsq9.fsf@gnu.org>
> Basically, set-window-configuration was called in a situation where it
> has only one valid buffer to play with, which is tough for its logic
> and the various other functions it invokes. The result was a bunch of
> bad windows with nil as their buffer.
If a live window has nil as its buffer, next redisplay will reliably
crash Emacs anyway. So this
/* We may have deleted windows above. Then again, maybe we
haven't: the functions we call to maybe delete windows can
decide a window cannot be deleted. Force recalculation of
Vwindow_list next time it is needed, to make sure stale
windows with no buffers don't escape into the wild, which
will cause crashes elsewhere. */
Vwindow_list = Qnil;
should not be needed. Otherwise we'd have been in serious trouble ever
since Vwindow_list was added. The earlier call
delete_all_child_windows (FRAME_ROOT_WINDOW (f));
should have reliably reset Vwindow_list to nil.
martin
next prev parent reply other threads:[~2022-12-17 9:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 17:04 bug#60096: 29.0.60; Crash in format_mode_line_unwind_data Juri Linkov
2022-12-15 21:42 ` Eli Zaretskii
2022-12-16 7:31 ` Juri Linkov
2022-12-16 11:46 ` Eli Zaretskii
2022-12-16 14:39 ` Eli Zaretskii
2022-12-16 15:03 ` Eli Zaretskii
2022-12-17 9:17 ` martin rudalics [this message]
2022-12-17 10:00 ` Eli Zaretskii
2022-12-17 10:53 ` Eli Zaretskii
2022-12-17 15:26 ` martin rudalics
2022-12-17 15:59 ` Eli Zaretskii
2022-12-17 17:05 ` martin rudalics
2022-12-17 17:52 ` Eli Zaretskii
2022-12-18 9:18 ` martin rudalics
2022-12-18 11:40 ` Eli Zaretskii
2022-12-17 17:23 ` Juri Linkov
2022-12-17 17:59 ` Eli Zaretskii
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=325aaa94-74fa-cf94-b66c-b87c69ebe386@gmx.at \
--to=rudalics@gmx.at \
--cc=60096@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
/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).