all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Gregory Heytings <gregory@heytings.org>,
	martin rudalics <rudalics@gmx.at>
Cc: luangruo@yahoo.com, 61704@debbugs.gnu.org
Subject: bug#61704: 29.0.60; Crash in get_narrowed_begv
Date: Wed, 22 Feb 2023 15:44:23 +0200	[thread overview]
Message-ID: <834jrdstl4.fsf@gnu.org> (raw)
In-Reply-To: <e737b605e91bf92bec61@heytings.org> (message from Gregory Heytings on Wed, 22 Feb 2023 13:17:27 +0000)

> Date: Wed, 22 Feb 2023 13:17:27 +0000
> From: Gregory Heytings <gregory@heytings.org>
> cc: luangruo@yahoo.com, 61704@debbugs.gnu.org
> 
> 
> >> How can len possibly be 0 at that point?  It is (in short) 
> >> window_body_width (w, WINDOW_BODY_IN_CANONICAL_CHARS) * 
> >> window_body_height (w, WINDOW_BODY_IN_CANONICAL_CHARS).  We could add a 
> >> condition in get_narrowed_len to return 1 when the result is 0, but it 
> >> could be a bug somewhere else (can a window body have a zero width 
> >> and/or height?), in which case it would be better to fix the bug there.
> >
> > I agree that we should understand how this happened (and asked a similar 
> > question), but I installed a defensive protection anyway.  It cannot do 
> > any harm.
> >
> 
> Okay.  Let's hope this will not hide another real bug.
> 
> I found a way to get such small windows: set window-min-width, 
> window-min-height, window-safe-min-width and window-safe-min-heigth to 0. 
> Of course doing that ignores the fact that the docstring of the 
> window-safe-min-* variables say that "Anything less might crash Emacs", 
> and that their values are 2 (width) and 1 (height).  Which makes me wonder 
> why these variables can be changed / exist.

Maybe Martin (CC'ed) can answer that.





  reply	other threads:[~2023-02-22 13:44 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <874jrdq4ct.fsf.ref@po-lus-librem-15.mail-host-address-is-not-set>
2023-02-22 12:20 ` bug#61704: 29.0.60; Crash in get_narrowed_begv Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-22 12:48   ` Gregory Heytings
2023-02-22 12:59     ` Eli Zaretskii
2023-02-22 13:16       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-22 13:40         ` Gregory Heytings
2023-02-22 13:47           ` Eli Zaretskii
2023-02-22 14:12           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-22 14:18             ` Gregory Heytings
2023-02-22 13:17       ` Gregory Heytings
2023-02-22 13:44         ` Eli Zaretskii [this message]
2023-02-23  9:33           ` martin rudalics
2023-02-23  9:37             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-23  9:46               ` martin rudalics
2023-02-23 13:07                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-23 15:28                   ` martin rudalics
2023-02-23 10:51               ` Eli Zaretskii
2023-02-23 13:08                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-23 10:54               ` Gregory Heytings
2023-02-23 13:11                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-23 13:23                   ` Gregory Heytings
2023-02-23 15:28                 ` martin rudalics
2023-02-23 15:54                   ` Gregory Heytings
2023-02-23 17:41                     ` martin rudalics
2023-02-23 10:44             ` Eli Zaretskii
2023-02-23 15:27               ` martin rudalics
2023-02-22 12:57   ` Eli Zaretskii
2023-02-22 13:23     ` Po Lu 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=834jrdstl4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=61704@debbugs.gnu.org \
    --cc=gregory@heytings.org \
    --cc=luangruo@yahoo.com \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.