Subject: Re: bug#43716: 28.0.50; Error with emacsclient <file>:

From: Lars Ingebrigtsen <[email-masked]>
Date: Wed, 30 Sep 2020 16:50:05 +0200

Tassilo Horn <[email-masked]> writes:

> I found it. :-)
>
> lib-src/emacsclient.c
> 2095               fprintf (stderr, "*ERROR*: %s", str);

Ah!  So the Emacs server reports it back to the client as an error.  No
wonder there's no backtrace here.  :-/

What about the following patch -- if that's the correct condition-case
that's catching all this, then it should give you a backtrace in the
server Emacs after reloading server.el.

diff --git a/lisp/server.el b/lisp/server.el
index a660deab8e..bdeed6bb00 100644
--- a/lisp/server.el
+++ b/lisp/server.el
@@ -1069,7 +1069,7 @@ server-process-filter
     (when prev
       (setq string (concat prev string))
       (process-put proc 'previous-string nil)))
-  (condition-case err
+  (condition-case-unless-debug err
       (progn
 	(server-add-client proc)
 	;; Send our pid

This is like the gazillionth time I've wanted a way to say (just when
debugging stuff like this) "there should be a way to disable all
condition case constructs"...

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no