From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Steven E. Harris" <seh@panix.com>
Cc: 59794@debbugs.gnu.org, Gerd Moellmann <gerd@gnu.org>
Subject: bug#59794: 29.0.60; NSport segfaults when a fullscreen frame is being closed)
Date: Wed, 11 Jan 2023 09:14:21 +0800 [thread overview]
Message-ID: <878ri9hnyq.fsf@yahoo.com> (raw)
In-Reply-To: <D1A91990-1A51-45F4-854B-4AF7B36A533F@panix.com> (Steven E. Harris's message of "Tue, 10 Jan 2023 15:35:04 -0500")
"Steven E. Harris" <seh@panix.com> writes:
> Using Emacs version 30.0.50 on macOS, reported by "emacs-version" as
>
> GNU Emacs 30.0.50 (build 1, x86_64-apple-darwin18.7.0, NS appkit-1671.60 Version 10.14.6 (Build 18G95)) of 2023-01-09
>
> for the “emacs-nightly” Homebrew formula, I find that this failure still occurs regularly, whether or not the frame being closed was full-screen
> or not. Specifically, when magit opens a new frame to capture a Git commit message, and I complete the message by pressing “C-c C-c,” the
> frame closes, and then Emacs crashes.
>
> Please find the captured crash report attached here.
Thanks, but please run Emacs under a debugger and send a backtrace from
there instead. I suspect this is a different bug.
GDB is supposedly not readily available for Mac OS anymore. Gerd, could
you please explain to Steven how to debug Emacs with lldb?
Thanks.
next prev parent reply other threads:[~2023-01-11 1:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 12:01 bug#59794: 29.0.60; NSport segfaults when a fullscreen frame is being closed Kai Ma
2022-12-03 10:08 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-03 10:27 ` Eli Zaretskii
2022-12-03 11:44 ` Gerd Möllmann
2022-12-03 13:03 ` Kai Ma
2022-12-03 13:53 ` Gerd Möllmann
2022-12-03 20:51 ` Kai Ma
[not found] ` <handler.59794.B.167005568724588.ack@debbugs.gnu.org>
2022-12-03 10:48 ` bug#59794: Acknowledgement (29.0.60; NSport segfaults when a fullscreen frame is being closed) Kai Ma
2022-12-04 6:54 ` bug#59794: 29.0.60; " Eli Zaretskii
2022-12-04 9:10 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-04 10:24 ` Eli Zaretskii
2022-12-04 11:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-04 12:21 ` Eli Zaretskii
2022-12-04 12:23 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-04 12:45 ` Kai Ma
2022-12-04 12:53 ` Eli Zaretskii
2022-12-04 13:53 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-04 14:04 ` Kai Ma
2022-12-05 1:10 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-10 20:35 ` Steven E. Harris
2023-01-11 1:14 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-01-11 4:38 ` Gerd Möllmann
2023-01-17 21:37 ` Steven E. Harris
2023-01-18 5:06 ` Gerd Möllmann
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=878ri9hnyq.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=59794@debbugs.gnu.org \
--cc=gerd@gnu.org \
--cc=luangruo@yahoo.com \
--cc=seh@panix.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).