all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Gregor Zattler <grfz@gmx.de>
Cc: 66978@debbugs.gnu.org
Subject: bug#66978: 30.0.50; crashed when closing one of two frames
Date: Tue, 07 Nov 2023 17:50:28 +0800	[thread overview]
Message-ID: <875y2dvqmz.fsf@yahoo.com> (raw)
In-Reply-To: <87zfzqsemc.fsf@no.lan> (Gregor Zattler's message of "Mon, 06 Nov 2023 23:26:03 +0100")

Gregor Zattler <grfz@gmx.de> writes:

> This (see below) is a backtrace from a crash after I
> closed one of two graphical frames associated with the
> same Emacs daemon.
>
> Tried to reproduce it, but couldn't, so don't know if
> this is helpful, if so I'm happy to answer questions,
> but the process is already killed.

If the core dump still remains, type:

   (gdb) p *(XErrorEvent *) 0x7fffffffbb70

and reply with the text thus printed.





  reply	other threads:[~2023-11-07  9:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06 22:26 bug#66978: 30.0.50; crashed when closing one of two frames Gregor Zattler
2023-11-07  9:50 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-11-07 12:20   ` Gregor Zattler
2023-11-07 12:24     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-07 13:48       ` Gregor Zattler
2023-11-08  0:49         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-08 16:05           ` Gregor Zattler
2023-11-08 23:52             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-10 11:01 ` Gregor Zattler
2023-11-10 12:07   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-21 15:28     ` Gregor Zattler

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875y2dvqmz.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=66978@debbugs.gnu.org \
    --cc=grfz@gmx.de \
    --cc=luangruo@yahoo.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.