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#47439: 27.2; In daemon mode, if after-init-hook errors out, the server does not start Date: Sun, 28 Mar 2021 17:05:12 +0300 Message-ID: <83zgynml0n.fsf@gnu.org> References: <87czvjs7pq.fsf@gnus.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="15457"; mail-complaints-to="usenet@ciao.gmane.io" Cc: gilles.usenet@gmail.com, 47439@debbugs.gnu.org To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Mar 28 16:06:10 2021 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 1lQW3N-0003vF-Qs for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 28 Mar 2021 16:06:09 +0200 Original-Received: from localhost ([::1]:55928 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lQW3M-0004UC-Rz for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 28 Mar 2021 10:06:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58088) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lQW3G-0004Tw-CE for bug-gnu-emacs@gnu.org; Sun, 28 Mar 2021 10:06:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:35129) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lQW3G-0001QN-5N for bug-gnu-emacs@gnu.org; Sun, 28 Mar 2021 10:06:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lQW3G-0001X7-0I for bug-gnu-emacs@gnu.org; Sun, 28 Mar 2021 10:06:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 28 Mar 2021 14:06:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 47439 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 47439-submit@debbugs.gnu.org id=B47439.16169403175840 (code B ref 47439); Sun, 28 Mar 2021 14:06:01 +0000 Original-Received: (at 47439) by debbugs.gnu.org; 28 Mar 2021 14:05:17 +0000 Original-Received: from localhost ([127.0.0.1]:46675 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lQW2X-0001W8-AA for submit@debbugs.gnu.org; Sun, 28 Mar 2021 10:05:17 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:36666) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lQW2U-0001Vt-OQ for 47439@debbugs.gnu.org; Sun, 28 Mar 2021 10:05:15 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:52745) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lQW2N-0000sH-LD; Sun, 28 Mar 2021 10:05:09 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:4294 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1lQW2M-0001Xo-AE; Sun, 28 Mar 2021 10:05:07 -0400 In-Reply-To: <87czvjs7pq.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun, 28 Mar 2021 15:56:01 +0200) 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:203165 Archived-At: > From: Lars Ingebrigtsen > Date: Sun, 28 Mar 2021 15:56:01 +0200 > Cc: 47439@debbugs.gnu.org > > There is no `condition-case' around the running of this hook; > therefore, if `debug-on-error' is non-nil, an error in one of > these functions will invoke the debugger. > --- > > So I think this is expected behaviour? Anybody got an opinion? The problem here is that if the daemon signals an error any place during startup before it starts the server, there's no way at all to communicate with the daemon, so you cannot know what happened and why. So I think we should provide one of the following, in case of such errors: . exit the daemon and leave the description of the problem on some disk file, or display it on the screen . start the server and allow clients to connect and see the error message, with or without the backtrace