From: Eli Zaretskii <eliz@gnu.org>
To: Andrii Kolomoiets <andreyk.mad@gmail.com>
Cc: fgunbin@fastmail.fm, 41184@debbugs.gnu.org
Subject: bug#41184: 28.0.50; Crash on NS when opening text file in a possibly invalid zip archive
Date: Mon, 11 May 2020 21:53:49 +0300 [thread overview]
Message-ID: <83d07a9ubm.fsf@gnu.org> (raw)
In-Reply-To: <m2blmu1f8x.fsf@gmail.com> (message from Andrii Kolomoiets on Mon, 11 May 2020 21:46:38 +0300)
> From: Andrii Kolomoiets <andreyk.mad@gmail.com>
> Cc: fgunbin@fastmail.fm, 41184@debbugs.gnu.org
> Date: Mon, 11 May 2020 21:46:38 +0300
>
> >> 4 AppKit 0x00007fff2fe991c4 -[NSWindow setTitle:] + 185
> >> 5 Emacs-x86_64-10_14 0x000000010b22dfb1 ns_set_name_internal + 161
> >> 6 Emacs-x86_64-10_14 0x000000010b227e8b ns_implicitly_set_name + 475
> >> 7 Emacs-x86_64-10_14 0x000000010b08a531 gui_consider_frame_title + 609
> >
> > Looks like some NS-specific issue with showing a strange file name in
> > the frame title?
>
> You are absolutely right.
>
> Actually crash can be reproduced with single step:
>
> (set-frame-name "\200")
It probably means the APIs used by ns_set_name_internal cannot handle
invalid UTF-8 sequences. The code there seems to naïvely encode in
UTF-8, but doesn't have any error handling for when that fails.
Someone who knows about NS programming should add some simple
workaround, like showing a string "\200" instead of a byte \200.
Or something.
next prev parent reply other threads:[~2020-05-11 18:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 1:52 bug#41184: 28.0.50; Crash on NS when opening text file in a possibly invalid zip archive Filipp Gunbin
2020-05-11 14:44 ` Eli Zaretskii
2020-05-11 15:57 ` Andrii Kolomoiets
2020-05-11 16:51 ` Eli Zaretskii
2020-05-11 18:46 ` Andrii Kolomoiets
2020-05-11 18:53 ` Eli Zaretskii [this message]
2020-05-12 10:44 ` Filipp Gunbin
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=83d07a9ubm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=41184@debbugs.gnu.org \
--cc=andreyk.mad@gmail.com \
--cc=fgunbin@fastmail.fm \
/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).