GNU bug report logs - #56528
29.0.50; Emacs lucid segfaults when X dies

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Po Lu <luangruo <at> yahoo.com>
Cc: 56528 <at> debbugs.gnu.org, visuweshm <at> gmail.com
Subject: bug#56528: 29.0.50; Emacs lucid segfaults when X dies
Date: Thu, 14 Jul 2022 08:36:29 +0300

> From: Po Lu <luangruo <at> yahoo.com>
> Cc: Visuwesh <visuweshm <at> gmail.com>,  56528 <at> debbugs.gnu.org
> Date: Thu, 14 Jul 2022 08:39:23 +0800
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > Btw, what do we expect Emacs to do in this scenario?  If the X server
> > is killed, Emacs cannot display anything, so why an abort is not TRT?
> > What practically interesting use case does this emulate?
> 
> It should just print an error message and die with a specific exit code,
> without printing a giant backtrace to stdout.

Print an error message where?

> Would binding `inhibit-redisplay' around the call to Fkill_emacs be a
> reasonable solution?

No, because that's not what inhibit-redisplay is for.

I think the right solution for this use case is to add a new command
that deletes all client frames.  We are talking about a user who
intentionally kills the X server, so the ability to conveniently
delete all the frames except the daemon frame will (or should) allow
Emacs to survive the traumatic event.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.