unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: kkylin@alum.mit.edu, 58857@debbugs.gnu.org
Subject: bug#58857: 28.2; Emacs on macOS seg faults when deleting fullscreen frame
Date: Sat, 29 Oct 2022 09:36:11 +0200	[thread overview]
Message-ID: <m2bkpvhyj8.fsf@Mini.fritz.box> (raw)
In-Reply-To: <83leozhyvw.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 29 Oct 2022 10:28:35 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Gerd Möllmann <gerd.moellmann@gmail.com>
>> (lldb) p emacsframe
>> (frame *) $64 = 0x000000012d811600
>> (lldb) p emacsframe->output_data
>> (output_data) $63 = {
>>   tty = nil
>>   x = nil
>>   w32 = nil
>>   ns = nil
>>   pgtk = nil
>>   haiku = nil
>> }
>
> So you are saying the NS-specific code that is run when Emacs is idle
> somehow references a frame that was deleted?

I interpret the backtrace as saying that it's handling an event
(AppKit`-[NSApplication(NSEvent)
_nextEventMatchingEventMask:untilDate:inMode:dequeue:]), and the GUI
frame has been deleted.

Don't know about the idle part.





  reply	other threads:[~2022-10-29  7:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-28 17:59 bug#58857: 28.2; Emacs on macOS seg faults when deleting fullscreen frame Kevin Lin
     [not found] ` <handler.58857.B.166701674619512.ack@debbugs.gnu.org>
2022-10-29  6:32   ` bug#58857: Acknowledgement (28.2; Emacs on macOS seg faults when deleting fullscreen frame) Kevin Lin
2022-10-29  6:39 ` bug#58857: 28.2; Emacs on macOS seg faults when deleting fullscreen frame Eli Zaretskii
2022-10-29  7:01   ` Gerd Möllmann
2022-10-29  7:28     ` Eli Zaretskii
2022-10-29  7:36       ` Gerd Möllmann [this message]
2022-10-29  8:04         ` Eli Zaretskii
2022-10-29  8:36     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-29 10:27     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-29 11:41       ` Gerd Möllmann
2022-10-29 11:59         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-29 12:19           ` Gerd Möllmann
2022-10-29 12:29             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-29 13:38               ` Gerd Möllmann
2022-11-13  4:11           ` 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=m2bkpvhyj8.fsf@Mini.fritz.box \
    --to=gerd.moellmann@gmail.com \
    --cc=58857@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=kkylin@alum.mit.edu \
    /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).