unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 13:55:10 -0500	[thread overview]
Message-ID: <CAHyO48zYAJnD2E3PPNRjOzoPYsj0qPacDmFH_scb-vZhve=qcw@mail.gmail.com> (raw)
In-Reply-To: <83imara6v0.fsf@gnu.org>

On Fri, Oct 30, 2020 at 1:47 PM Eli Zaretskii <eliz@gnu.org> wrote:
> That doesn't sound like a frame that is not live, that sounds like a
> frame whose memory was freed.  Or a frame pointer that is just
> garbage.
>
> So the question now is: where did that frame pointer come from?

Good question--how might I debug that next time it happens?





  reply	other threads:[~2020-10-30 18:55 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
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 [this message]
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

  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='CAHyO48zYAJnD2E3PPNRjOzoPYsj0qPacDmFH_scb-vZhve=qcw@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 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).