From: Eli Zaretskii <eliz@gnu.org>
To: Spencer Baugh <sbaugh@janestreet.com>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 65897@debbugs.gnu.org
Subject: bug#65897: 29.1.50; Debugging errors surfaced through emacsclient is hard
Date: Thu, 14 Sep 2023 17:54:28 +0300 [thread overview]
Message-ID: <83msxols9n.fsf@gnu.org> (raw)
In-Reply-To: <iery1hb9o0i.fsf@janestreet.com> (message from Spencer Baugh on Tue, 12 Sep 2023 15:42:37 -0400)
> From: Spencer Baugh <sbaugh@janestreet.com>
> Date: Tue, 12 Sep 2023 15:42:37 -0400
>
> Toy example:
> 1. emacs -Q
> 2. (server-start)
> 3. (add-hook 'before-make-frame-hook (lambda () (error "frame hook error")))
> 4. emacsclient -c
>
> The output of emacsclient is:
>
> Waiting for Emacs...
> *ERROR*: frame hook error
>
> That's all, there is no way to get more information about the error that
> happened.
>
> Ideally, when emacsclient encounters an error and debug-on-error is
> non-nil, it should cause Emacs to enter the debugger.
I'm not sure we can allow entering the debugger from server-execute.
That function is documented as being called from timers and process
filters, so entering the debugger might be unsafe.
Stefan, any comments?
next prev parent reply other threads:[~2023-09-14 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 19:42 bug#65897: 29.1.50; Debugging errors surfaced through emacsclient is hard Spencer Baugh
2023-09-14 14:54 ` Eli Zaretskii [this message]
2023-09-18 14:00 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83msxols9n.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65897@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=sbaugh@janestreet.com \
/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).