From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gerd@gnu.org, gongqijian@gmail.com, 74274@debbugs.gnu.org
Subject: bug#74274: [PATCH] Revert part of d3f8ed730f to avoid segmentation fault
Date: Sun, 10 Nov 2024 11:56:07 +0100 [thread overview]
Message-ID: <m2cyj3nyrc.fsf@gmail.com> (raw)
In-Reply-To: <m21pzk7qz4.fsf@gmail.com> ("Gerd Möllmann"'s message of "Sat, 09 Nov 2024 09:26:23 +0100")
Gerd Möllmann <gerd.moellmann@gmail.com> writes:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>> Should this perhaps have an eassert which verifies that every glyph
>> has a valid frame pointer? At the very least please add a comment
>> there explaining the need for the enabled_p test and mentioning the
>> frame pointer of the glyphs.
>
> I don't know. It's one of the most basic things about the meaning of
> enabled_p in current glyphs, and it's not limited the frame pointer in
> any way.
Found another case of copying from non-enabled glyphs. Reproducable with
emacs -q -l with a file containing
(with-current-buffer (get-buffer-create "1")
(setq header-line-format
'((:eval (format "*package*: - symbol-packages: - lexical-binding: %s"
lexical-binding)))))
(with-current-buffer (get-buffer-create "2")
(insert "something"))
(let ((w1 (selected-window))
(w2 (split-window-right)))
(set-window-buffer w1 (get-buffer "1"))
(set-window-buffer w2 (get-buffer "2"))
(message "message"))
It's a 30 years old bug, so it isn't something urgent to fix.
I'll port something to savannah as soon as I find the time.
next prev parent reply other threads:[~2024-11-10 10:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 6:31 bug#74274: [PATCH] Revert part of d3f8ed730f to avoid segmentation fault Gong Qijian
2024-11-09 4:15 ` Gerd Möllmann
2024-11-09 6:10 ` qijian gong
2024-11-09 6:59 ` Gerd Möllmann
2024-11-09 7:23 ` Gerd Möllmann
2024-11-09 8:02 ` Gerd Möllmann
2024-11-09 8:17 ` Eli Zaretskii
2024-11-09 8:26 ` Gerd Möllmann
2024-11-10 10:56 ` Gerd Möllmann [this message]
2024-11-10 19:06 ` Gerd Möllmann
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=m2cyj3nyrc.fsf@gmail.com \
--to=gerd.moellmann@gmail.com \
--cc=74274@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gerd@gnu.org \
--cc=gongqijian@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).