From: Andrii Kolomoiets <andreyk.mad@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Filipp Gunbin <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 18:57:52 +0300 [thread overview]
Message-ID: <m2imh2lb0f.fsf@gmail.com> (raw)
In-Reply-To: <83v9l2bkg5.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 11 May 2020 17:44:10 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> - emacs -Q
>> - C-x C-f <path to attached zip> RET
>> - RET on the first file in archive (the one with .txt extension)
>
> Can you please show the backtrace? Without that, the bug report is
> only useful if the crash can be reproduced, and you shouldn't rely on
> that (e.g, I couldn't reproduce it).
For this time not only the subject contains "NS" but also the message
body contains "Mac OS X" ;-)
Can reproduce it with those steps. Here is backtrace:
Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Invalid parameter not satisfying: aString != nil'
abort() called
terminating with uncaught exception of type NSException
Application Specific Backtrace 1:
0 CoreFoundation 0x00007fff32c47d07 __exceptionPreprocess + 250
1 libobjc.A.dylib 0x00007fff6b96b5bf objc_exception_throw + 48
2 CoreFoundation 0x00007fff32c70ec8 +[NSException raise:format:arguments:] + 88
3 Foundation 0x00007fff3535bf3d -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 191
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
8 Emacs-x86_64-10_14 0x000000010b05f9fc redisplay_internal + 1324
9 Emacs-x86_64-10_14 0x000000010b0fdbe5 read_char + 2213
10 Emacs-x86_64-10_14 0x000000010b0fb7aa read_key_sequence + 1722
11 Emacs-x86_64-10_14 0x000000010b0f9fac command_loop_1 + 1340
12 Emacs-x86_64-10_14 0x000000010b180b87 internal_condition_case + 263
13 Emacs-x86_64-10_14 0x000000010b10a120 command_loop_2 + 48
14 Emacs-x86_64-10_14 0x000000010b1803ab internal_catch + 267
15 Emacs-x86_64-10_14 0x000000010b24c385 command_loop.cold.1 + 69
16 Emacs-x86_64-10_14 0x000000010b0f9073 command_loop + 131
17 Emacs-x86_64-10_14 0x000000010b0f8fa3 recursive_edit_1 + 115
18 Emacs-x86_64-10_14 0x000000010b0f91fb Frecursive_edit + 347
19 Emacs-x86_64-10_14 0x000000010b0f7dd7 main + 7431
20 libdyld.dylib 0x00007fff6cb12cc9 start + 1
--
Andrii
next prev parent reply other threads:[~2020-05-11 15:57 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 [this message]
2020-05-11 16:51 ` Eli Zaretskii
2020-05-11 18:46 ` Andrii Kolomoiets
2020-05-11 18:53 ` Eli Zaretskii
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=m2imh2lb0f.fsf@gmail.com \
--to=andreyk.mad@gmail.com \
--cc=41184@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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).