From: "Clément Pit--Claudel" <clement.pit@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: How can I rethrow an error after recording a backtrace?
Date: Sat, 6 Aug 2016 11:24:03 -0400 [thread overview]
Message-ID: <b113a92c-677f-4086-b67b-1541f447eda7@gmail.com> (raw)
In-Reply-To: <83zioqjjve.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 1321 bytes --]
On 2016-08-06 06:02, Eli Zaretskii wrote:
>> Cc: emacs-devel@gnu.org
>> From: Clément Pit--Claudel <clement.pit@gmail.com>
>> Date: Fri, 5 Aug 2016 11:38:14 -0400
>>
>> On 2016-08-05 09:40, Eli Zaretskii wrote:
>>> But with -daemon, even the first invocation of emacsclient already
>>> doesn't display the backtrace, right? So there's still something
>>> different between these two use cases.
>>
>> Well, it depends what you mean by "display the backtrace": the server doesn't respect debug-on-error
>
> Why doesn't it? Isn't that already a bug?
I think you confirmed that it was in the other "Backtraces on server?" thread?
>> but if I register my own debugger, then I *can* capture the first backtrace. I have attached a file cpc-server.el that will explain the issue better than I can explain it in words (thanks for your patience!). Here's how it's used:
>
> So you are saying that the problem is the daemon doesn't increment
> num-nonmacro-input-events for each new connection? That should be
> easy enough to fix, isn't it?
Yes, but I fear it wouldn't cover the following case:
(condition-case err1
(condition-case err2
(error "A")
(error (error "B)))
(error (message "Oups")))
Only the first error would be captured by the debugger.
Clément.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-08-06 15:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 2:12 How can I rethrow an error after recording a backtrace? Clément Pit--Claudel
2016-08-05 2:23 ` Stefan Monnier
2016-08-05 9:40 ` Clément Pit--Claudel
2016-08-06 2:11 ` Stefan Monnier
2016-08-06 10:03 ` Eli Zaretskii
2016-08-06 13:29 ` Stefan Monnier
2016-08-05 2:34 ` Clément Pit--Claudel
2016-08-05 6:12 ` Eli Zaretskii
[not found] ` <73dc7988-7b41-385d-1083-6a6fa4bfbd91@gmail.com>
2016-08-05 13:40 ` Eli Zaretskii
2016-08-05 15:38 ` Clément Pit--Claudel
2016-08-06 10:02 ` Eli Zaretskii
2016-08-06 15:24 ` Clément Pit--Claudel [this message]
2016-08-06 15:31 ` Eli Zaretskii
2016-08-06 15:49 ` Clément Pit--Claudel
2016-08-06 17:38 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b113a92c-677f-4086-b67b-1541f447eda7@gmail.com \
--to=clement.pit@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.