From: Aaron Jensen <aaronjensen@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 44313@debbugs.gnu.org
Subject: bug#44313: 27.1.50; ns_mouse_position EXC_BAD_ACCESS crash
Date: Fri, 30 Oct 2020 05:16:35 -0500 [thread overview]
Message-ID: <CAHyO48x_tH9MQWxAmCaGvk5GRYNeBfQKBq7tW1R2oGQ7RkWTmw@mail.gmail.com> (raw)
In-Reply-To: <83o8kkb2vr.fsf@gnu.org>
On Fri, Oct 30, 2020 at 2:16 AM Eli Zaretskii <eliz@gnu.org> wrote:
> The crash is in frame #0, so please show the relevant variables
> there.
Okay, next time it crashes I will get what I can.
> According to the line number the crash is here:
>
> if (f && FRAME_NS_P (f))
>
> So why does FRAME_NS_P crash? which part of the frame's structure are
> invalid?
I believe that macro is defined as:
#define FRAME_NS_P(f) ((f)->output_method == output_ns)
Would the de-reference cause an EXC_BAD_ACCESS if the frame had been released?
I make use of child frames via the posframe packages. I wonder if
something requested a mouse pixel position for a frame either as it
was being released or after it was being released?
next prev parent reply other threads:[~2020-10-30 10:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 20:16 bug#44313: 27.1.50; ns_mouse_position EXC_BAD_ACCESS crash Aaron Jensen
2020-10-30 7:15 ` Eli Zaretskii
2020-10-30 10:16 ` Aaron Jensen [this message]
2020-10-30 11:29 ` Eli Zaretskii
2020-10-30 15:54 ` Aaron Jensen
2020-10-30 18:47 ` Eli Zaretskii
2020-10-30 18:55 ` Aaron Jensen
2020-10-30 19:07 ` Eli Zaretskii
2020-10-30 19:37 ` Aaron Jensen
2020-10-30 20:12 ` Eli Zaretskii
2020-10-30 20:18 ` Aaron Jensen
2020-10-30 22:35 ` Alan Third
2020-11-02 18:11 ` Aaron Jensen
2020-11-06 14:29 ` Aaron Jensen
2020-11-07 16:29 ` Alan Third
2020-11-09 14:43 ` Lars Ingebrigtsen
2020-11-09 14:54 ` Alan Third
2020-12-12 10:43 ` Alan Third
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHyO48x_tH9MQWxAmCaGvk5GRYNeBfQKBq7tW1R2oGQ7RkWTmw@mail.gmail.com \
--to=aaronjensen@gmail.com \
--cc=44313@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.