From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: gilles.usenet@gmail.com, 47439@debbugs.gnu.org
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 [thread overview]
Message-ID: <83zgynml0n.fsf@gnu.org> (raw)
In-Reply-To: <87czvjs7pq.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun, 28 Mar 2021 15:56:01 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> 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
next prev parent reply other threads:[~2021-03-28 14:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 1:00 bug#47439: 27.2; In daemon mode, if after-init-hook errors out, the server does not start Gilles
2021-03-28 13:56 ` Lars Ingebrigtsen
2021-03-28 14:05 ` Eli Zaretskii [this message]
2021-03-28 14:43 ` Lars Ingebrigtsen
2021-03-28 14:55 ` Eli Zaretskii
2021-03-28 14:56 ` Lars Ingebrigtsen
2021-03-28 17:04 ` Gilles
2021-03-28 17:23 ` Eli Zaretskii
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=83zgynml0n.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=47439@debbugs.gnu.org \
--cc=gilles.usenet@gmail.com \
--cc=larsi@gnus.org \
/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).