From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 56528@debbugs.gnu.org, Visuwesh <visuweshm@gmail.com>
Subject: bug#56528: 29.0.50; Emacs lucid segfaults when X dies
Date: Thu, 14 Jul 2022 09:04:49 +0800 [thread overview]
Message-ID: <87y1wwsdvy.fsf@yahoo.com> (raw)
In-Reply-To: <83v8s1uecy.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 13 Jul 2022 20:11:41 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> That's probably just sheer luck. When you kill the X server, any code
> in Emacs that tries to display something will crash and burn, because
> there's generally no way for us to display anything in that case.
Not exactly. When the connection to the X server is lost, any attempt
to communicate with it will result in the IO error handler being called.
We install an error handler that performs the following:
- Bind `inhibit-redisplay' to t.
- Delete each frame on the display that went down.
- Free the display data and delete the terminal.
- Kill Emacs if no terminals are left.
- Throw an error to get Emacs out of the error handler.
Unfortunately, that doesn't always work reliably, such as here. And
we're trying to find out why.
next prev parent reply other threads:[~2022-07-14 1:04 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 4:32 bug#56528: 29.0.50; Emacs lucid segfaults when X dies visuweshm
2022-07-13 10:45 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-13 11:05 ` Visuwesh
2022-07-13 12:17 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-13 13:06 ` Visuwesh
2022-07-13 13:13 ` Eli Zaretskii
2022-07-13 13:15 ` Eli Zaretskii
2022-07-13 13:23 ` Visuwesh
2022-07-13 13:49 ` Eli Zaretskii
2022-07-13 14:18 ` Visuwesh
2022-07-13 17:11 ` Eli Zaretskii
2022-07-13 17:18 ` Eli Zaretskii
2022-07-13 17:29 ` Visuwesh
2022-07-13 17:54 ` Eli Zaretskii
2022-07-13 17:20 ` Visuwesh
2022-07-13 17:50 ` Eli Zaretskii
2022-07-14 1:06 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 5:41 ` Eli Zaretskii
2022-07-14 6:27 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 7:18 ` Eli Zaretskii
2022-07-14 1:04 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-07-14 5:39 ` Eli Zaretskii
2022-07-14 6:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 7:18 ` Eli Zaretskii
2022-07-14 7:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-15 16:17 ` Andrés Ramírez
2022-07-16 3:17 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 0:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 5:36 ` Eli Zaretskii
2022-07-14 6:24 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 3:47 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 4:24 ` Visuwesh
2022-07-14 4:52 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 5:37 ` Visuwesh
2022-07-14 6:25 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87y1wwsdvy.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=56528@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
--cc=visuweshm@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).