From: Eli Zaretskii <eliz@gnu.org>
To: Sami Lahtinen <sami.lahtinen@gmail.com>
Cc: 62831@debbugs.gnu.org
Subject: bug#62831: 29.0.90; Emacs-pretest-29.0.90 aarch64 on macOS crashes when receiving a three-finger tap.
Date: Fri, 14 Apr 2023 16:44:57 +0300 [thread overview]
Message-ID: <83h6tifuhy.fsf@gnu.org> (raw)
In-Reply-To: <CAK_WPLuPi14nG9QB5z8J6guEwvx+ZGhoEws2rAUG7AKWYhitdw@mail.gmail.com> (message from Sami Lahtinen on Fri, 14 Apr 2023 15:46:28 +0300)
> From: Sami Lahtinen <sami.lahtinen@gmail.com>
> Date: Fri, 14 Apr 2023 15:46:28 +0300
>
> I will attach an .ips file from ~/Library/Logs/DiagnosticReports/ I hope this is what you are looking for,
> if not, can you please specify?
I meant the backtrace reported by a debugger. Run Emacs under a
debugger, either GDB (preferred) or LLDB, and when Emacs crashes
produce the backtrace and post it. In GDB, the command to display a
backtrace is "backtrace", or "bt" in short. I don't know what is the
command in LLDB, sorry.
> My Emacs is the binary from emacsformacosx.com as-is. As far as I know, it is compiled without
> changes.
Does that site say anywhere if there are some changes?
next prev parent reply other threads:[~2023-04-14 13:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 8:16 bug#62831: 29.0.90; Emacs-pretest-29.0.90 aarch64 on macOS crashes when receiving a three-finger tap Sami Lahtinen
2023-04-14 12:26 ` Eli Zaretskii
[not found] ` <CAK_WPLuPi14nG9QB5z8J6guEwvx+ZGhoEws2rAUG7AKWYhitdw@mail.gmail.com>
2023-04-14 13:44 ` Eli Zaretskii [this message]
2023-04-14 14:06 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-15 16:49 ` Sami Lahtinen
2023-04-15 19:50 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-16 6:43 ` Sami Lahtinen
2023-04-16 14:56 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-16 17:07 ` Sami Lahtinen
2023-04-16 17:21 ` Eli Zaretskii
2023-04-16 17:29 ` Sami Lahtinen
2023-04-16 18:16 ` Sami Lahtinen
2023-09-11 23:24 ` Stefan Kangas
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=83h6tifuhy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62831@debbugs.gnu.org \
--cc=sami.lahtinen@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).