From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: ravine.var@gmail.com, 39892@debbugs.gnu.org
Subject: bug#39892: 28.0.50; Crash when running async command
Date: Thu, 05 Mar 2020 11:57:24 +0100 [thread overview]
Message-ID: <m24kv3t6gb.fsf@gmail.com> (raw)
In-Reply-To: <83r1y7uoa4.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 05 Mar 2020 11:46:59 +0200")
>>>>> On Thu, 05 Mar 2020 11:46:59 +0200, Eli Zaretskii <eliz@gnu.org> said:
Eli> How about the patch below? It works for me, and seems to be TRT in
Eli> general, since it makes the code more defensive in the face of
Eli> possible nil values in that vector, which are legitimate according to
Eli> my reading of the commentary at the beginning of fontset.c.
That patch works for me.
>> Btw, U+E9F8 is a PUA character; how did it get into a context where we
>> are trying to display it?
Eli> I'd still like to know the answer to this. It seems like something
Eli> fishy is going on in the original use case that requires us to try to
Eli> display this PUA codepoint.
Itʼs essentially doing 'cat' on a .gz file. Thereʼs no guarantee
whatsoever that the result is valid. And in fact doing exactly that
crashes the same way (without the patch).
Interestingly, under macOS it displays a proper glyph using
"mac-ct:-*-Hannotate TC-normal-normal-normal-*-14-*-*-*-p-0-iso10646-1
(#x933F)", so somebody has decided that codepoint is good for something.
Robert
next prev parent reply other threads:[~2020-03-05 10:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 2:37 bug#39892: 28.0.50; Crash when running async command Ravine Var
2020-03-04 10:01 ` Robert Pluim
2020-03-04 16:13 ` Eli Zaretskii
2020-03-05 9:46 ` Eli Zaretskii
2020-03-05 10:57 ` Robert Pluim [this message]
2020-03-05 11:22 ` Eli Zaretskii
2020-03-05 15:21 ` Ravine Var
2020-03-05 15:59 ` Eli Zaretskii
2020-03-05 15:24 ` Ravine Var
2020-03-05 15:53 ` 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=m24kv3t6gb.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=39892@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=ravine.var@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).