all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Gregory Heytings <gregory@heytings.org>
To: Po Lu <luangruo@yahoo.com>
Cc: martin rudalics <rudalics@gmx.at>, Eli Zaretskii <eliz@gnu.org>,
	61704@debbugs.gnu.org
Subject: bug#61704: 29.0.60; Crash in get_narrowed_begv
Date: Thu, 23 Feb 2023 10:54:25 +0000	[thread overview]
Message-ID: <96b742a05d29fcf9a7d7@heytings.org> (raw)
In-Reply-To: <87bklkoh77.fsf@yahoo.com>


>> and OTOH the redisplay engine should be able to handle zero window 
>> sizes to avoid crashes the window code cannot prevent.
>
> This is the only reasonable approach under X.
>

I maintain that the bug is (was) most probably not in get_narrowed_*.  I 
just built Emacs with the GTK, Lucid and no toolkits, I disabled 
everything (tool-bar, menu-bar, scroll-bar, fringe-mode 0), and even with 
that, after resizing the Emacs frame until it is literally a single pixel 
on screen, I'm not able to get (under emacs -Q) a window width or a height 
equal to 0 there.  The smallest values I get are width = 2 and height = 1.

That, the fact that this code has been there for a half year without a 
single reported crash (if resizing a window is enough to trigger such a 
crash, that would surely have happened already), and the fact that 
get_narrowed_* is not executed at all in the ediff control frame, means 
that there is a bug somewhere else.






  parent reply	other threads:[~2023-02-23 10:54 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
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 [this message]
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=96b742a05d29fcf9a7d7@heytings.org \
    --to=gregory@heytings.org \
    --cc=61704@debbugs.gnu.org \
    --cc=eliz@gnu.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.