From: Po Lu <luangruo@yahoo.com>
To: Perry Smith <pedzsan@icloud.com>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs on macOS
Date: Fri, 01 Apr 2022 15:55:05 +0800 [thread overview]
Message-ID: <87czi1i6g6.fsf@yahoo.com> (raw)
In-Reply-To: <0CBBB7FB-1D2A-46C7-90C2-8664913B0E29@icloud.com> (Perry Smith's message of "Thu, 31 Mar 2022 17:52:01 -0500")
Perry Smith <pedzsan@icloud.com> writes:
> When emacs dies on a Mac (as with any application), a GUI window pops
> up with a place to enter some text and a button that says “Report”.
> When the button is hit, something sends something somewhere but I
> doubt if anything is sent to the emacs-bug list. The window appears
> to have some pretty useful information like stack trace for each
> thread, etc.
>
> The flip side is, report-emacs-bug also has a lot of useful
> information. My question is what is the preferred or most effective
> way to combine these two sources of information? One choice is to
> copy what is in the macOS window and paste it into the email that
> report-emacs-bug creates. Another choice might be to attach a file
> that macOS creates when an application dies but I don’t know where
> that file lives.
When Emacs crashes, it should output a backtrace to stdout. The correct
thing to do is to ignore the contents of any macOS system error dialog,
convert the backtrace to human-readable form, and send that backtrace to
bug-gnu-emacs along with the output of `report-emacs-bug'.
See (emacs)Crashing for more information on how to do this.
next prev parent reply other threads:[~2022-04-01 7:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 22:52 Emacs on macOS Perry Smith
2022-04-01 7:55 ` Po Lu [this message]
2022-04-01 10:47 ` Eli Zaretskii
2022-04-03 7:04 ` [Add xattr to the INSTALLATION file?] (was: Emacs on macOS) Uwe Brauer
2022-04-03 13:45 ` Emacs on macOS Alan Third
2022-04-03 17:20 ` [script vs ICon: latex binaries not found] (was: Emacs on macOS) Uwe Brauer
[not found] ` <m2k0c6ozgm.fsf@mat.ucm.es>
2022-04-04 3:05 ` chad
2022-04-04 8:38 ` Tim Cross
2022-04-04 20:06 ` [script vs ICon: latex binaries not found] Uwe Brauer
2022-04-04 20:03 ` Uwe Brauer
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=87czi1i6g6.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=emacs-devel@gnu.org \
--cc=pedzsan@icloud.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).