From: Eli Zaretskii <eliz@gnu.org>
To: Aaron Jensen <aaronjensen@gmail.com>
Cc: 30800@debbugs.gnu.org
Subject: bug#30800: 26.0.91; unknown crash on macos
Date: Wed, 21 Mar 2018 08:37:52 +0200 [thread overview]
Message-ID: <83fu4ukk73.fsf@gnu.org> (raw)
In-Reply-To: <CAHyO48yv7Wib9_odP_mmZ5gKGMXu-UJkcMgSRqsQCnWu6svKig@mail.gmail.com> (message from Aaron Jensen on Tue, 20 Mar 2018 16:39:52 -0700)
> From: Aaron Jensen <aaronjensen@gmail.com>
> Date: Tue, 20 Mar 2018 16:39:52 -0700
>
> Emacs is crashing more often today with this crash. Here is another
> trace. Again, it's the `FRAME_NS_VIEW (represented_frame)' that is
> crashing:
>
> * thread #1, queue = 'com.apple.main-thread', stop reason =
> EXC_BAD_ACCESS (code=1, address=0x0)
> * frame #0: 0x00000001003aadbb emacs`-[EmacsApp
> sendEvent:](self=0x00000001018285e0, _cmd="sendEvent:",
> theEvent=0x000000011a202f40) at nsterm.m:5449
>
> frame #0: 0x00000001003aadbb emacs`-[EmacsApp
> sendEvent:](self=0x00000001018285e0, _cmd="sendEvent:",
> theEvent=0x000000011a202f40) at nsterm.m:5449
> 5446 if (represented_filename != nil && represented_frame)
> 5447 {
> 5448 NSString *fstr = represented_filename;
> -> 5449 NSView *view = FRAME_NS_VIEW (represented_frame);
> 5450 #ifdef NS_IMPL_COCOA
Which part of FRAME_NS_VIEW causes the crash? There are 2
dereferences there; which one is the culprit?
next prev parent reply other threads:[~2018-03-21 6:37 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 16:18 bug#30800: 26.0.91; unknown crash on macos Aaron Jensen
2018-03-13 16:36 ` Aaron Jensen
2018-03-20 23:39 ` Aaron Jensen
2018-03-21 6:37 ` Eli Zaretskii [this message]
2018-03-21 16:25 ` Aaron Jensen
2018-03-21 17:00 ` Eli Zaretskii
2018-03-21 17:09 ` Eli Zaretskii
2018-03-21 17:31 ` Aaron Jensen
2018-03-21 18:22 ` Eli Zaretskii
2018-03-21 18:31 ` Aaron Jensen
2018-03-21 18:48 ` Eli Zaretskii
2018-03-21 19:19 ` Alan Third
2018-03-21 19:36 ` Eli Zaretskii
2018-03-21 20:12 ` Alan Third
2018-03-22 5:40 ` Aaron Jensen
2018-03-22 7:26 ` Eli Zaretskii
2018-03-22 15:39 ` Aaron Jensen
2018-03-22 15:57 ` Eli Zaretskii
2018-03-23 1:49 ` Aaron Jensen
2018-03-23 8:16 ` Eli Zaretskii
2018-03-23 19:52 ` Alan Third
2018-03-23 20:57 ` Aaron Jensen
2018-03-24 7:20 ` Aaron Jensen
2018-03-24 10:29 ` Alan Third
2018-03-24 14:54 ` Eli Zaretskii
2018-03-24 16:18 ` Alan Third
2018-03-24 17:48 ` Eli Zaretskii
2018-03-25 19:17 ` Alan Third
2018-03-24 10:49 ` Charles A. Roelli
2018-03-24 14:12 ` Alan Third
2018-03-25 20:14 ` Charles A. Roelli
2018-03-26 18:37 ` Alan Third
2018-03-26 23:03 ` Aaron Jensen
2018-03-30 11:37 ` Alan Third
2018-03-30 11:57 ` Aaron Jensen
2018-03-22 5:35 ` Aaron Jensen
2018-03-22 7:16 ` 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=83fu4ukk73.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30800@debbugs.gnu.org \
--cc=aaronjensen@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).