From: Kai Ma <justksqsf@gmail.com>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: 59794@debbugs.gnu.org, eliz@gnu.org
Subject: bug#59794: 29.0.60; NSport segfaults when a fullscreen frame is being closed
Date: Sun, 4 Dec 2022 04:51:18 +0800 [thread overview]
Message-ID: <C6772904-5AD3-42A0-B70F-DF39EBE0EADF@gmail.com> (raw)
In-Reply-To: <99841eb7-fda0-517a-2454-79b8c5e29991@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 618 bytes --]
> On Dec 3, 2022, at 21:53, Gerd Möllmann <gerd.moellmann@gmail.com> wrote:
>
> On 03.12.22 14:03, Kai Ma wrote:
>>> On Dec 3, 2022, at 19:44, Gerd Möllmann <gerd.moellmann@gmail.com> wrote:
>>>
>>> FWIW, no crash here with dd7a7633bebc4db5caca3898bf318721f1f370c8 (master), macOS 13.0.1, ASAN enabled.
>> Weird. I tested this commit with the default configure options and it segfaulted. How to enable ASAN?
>
> I forgot to mentions that I have an M1 here, maybe it's that.
Thanks! I tried again with your configure options, but Emacs still crashed here. :-(
I guess this is indeed the reason.
[-- Attachment #2: Type: text/html, Size: 1403 bytes --]
next prev parent reply other threads:[~2022-12-03 20:51 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 [this message]
[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
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=C6772904-5AD3-42A0-B70F-DF39EBE0EADF@gmail.com \
--to=justksqsf@gmail.com \
--cc=59794@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gerd.moellmann@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).