From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#56528: 29.0.50; Emacs lucid segfaults when X dies Date: Thu, 14 Jul 2022 08:36:29 +0300 Message-ID: <837d4guug2.fsf@gnu.org> References: <877d4h1vl9.fsf@astatine.mail-host-address-is-not-set> <87ilo1uw9d.fsf@yahoo.com> <87sfn5l1c9.fsf@gmail.com> <87cze9urzv.fsf@yahoo.com> <877d4hi2lx.fsf@gmail.com> <831qupw3us.fsf@gnu.org> <874jzkv878.fsf@yahoo.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33481"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 56528@debbugs.gnu.org, visuweshm@gmail.com To: Po Lu Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Jul 14 07:50:34 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oBrkA-0008aA-K2 for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 14 Jul 2022 07:50:34 +0200 Original-Received: from localhost ([::1]:36992 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oBrk7-0007sV-DF for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 14 Jul 2022 01:50:33 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:45986) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oBrX3-00010o-TJ for bug-gnu-emacs@gnu.org; Thu, 14 Jul 2022 01:37:01 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:54499) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oBrX3-0004se-KR for bug-gnu-emacs@gnu.org; Thu, 14 Jul 2022 01:37:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oBrX3-0004Up-I3 for bug-gnu-emacs@gnu.org; Thu, 14 Jul 2022 01:37:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 14 Jul 2022 05:37:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 56528 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 56528-submit@debbugs.gnu.org id=B56528.165777702017276 (code B ref 56528); Thu, 14 Jul 2022 05:37:01 +0000 Original-Received: (at 56528) by debbugs.gnu.org; 14 Jul 2022 05:37:00 +0000 Original-Received: from localhost ([127.0.0.1]:48396 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oBrX0-0004UY-7f for submit@debbugs.gnu.org; Thu, 14 Jul 2022 01:36:59 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:33044) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oBrWk-0004U4-Ek for 56528@debbugs.gnu.org; Thu, 14 Jul 2022 01:36:56 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:37856) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oBrWe-0004px-Ro; Thu, 14 Jul 2022 01:36:36 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=G41b8jalpvayMUzDgwni3O43MANc3jRk/PgNXPQb80o=; b=m8PhLQqzwBBv vPCz2W6jFXgL7wACBYjeIVMKKHdF9osCkTdKiU6fsJ88t1+1Sk2yd91G5K20nfFy98OQ1H6QRh7mP 5xraTKiAb8Zsqxl931A9IXxg+O1I4zk1DMouypUG6iaCPivm2Q4J2OTOb1UGbrGls94mTLnehtasm pRiYwbembTLp8sYABfsbWtDxFzjDh9+8OlV4byoamNzyQZnuKyUpQEoKLbBn+n2O2B6sK1C0U4xUE hux/E+sTynx+tw2PIP/K/69FE8tDC8wNwDL/KObGtfRnwimfR/XREQhopCEu7puowEKHxMujQnvi6 jDP6+FW9EZvz8yo0FR+CYw==; Original-Received: from [87.69.77.57] (port=3931 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oBrWd-0006Xe-Q5; Thu, 14 Jul 2022 01:36:36 -0400 In-Reply-To: <874jzkv878.fsf@yahoo.com> (message from Po Lu on Thu, 14 Jul 2022 08:39:23 +0800) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:236951 Archived-At: > From: Po Lu > Cc: Visuwesh , 56528@debbugs.gnu.org > Date: Thu, 14 Jul 2022 08:39:23 +0800 > > Eli Zaretskii 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.