From: "Ludovic Courtès" <ludo@gnu.org>
To: 40016@debbugs.gnu.org
Cc: Christopher Baines <mail@cbaines.net>
Subject: [bug#40016] [PATCH] inferior: Distinguish inferior exceptions.
Date: Tue, 10 Mar 2020 18:30:48 +0100 [thread overview]
Message-ID: <878sk8t8vr.fsf@gnu.org> (raw)
In-Reply-To: <20200310160305.15865-1-ludo@gnu.org> ("Ludovic \=\?utf-8\?Q\?Cou\?\= \=\?utf-8\?Q\?rt\=C3\=A8s\=22's\?\= message of "Tue, 10 Mar 2020 17:03:05 +0100")
Hello,
Ludovic Courtès <ludo@gnu.org> skribis:
> This avoids ambiguities when looking at a backtrace where the exception
> was actually thrown by an inferior in a very different context.
The idea was suggested at the Guix Days by someone who had had a hard
time looking at one of these weird backtraces, until you realize the
exception was actually thrown by another process.
There are a few places in the Data Service that do things like:
(catch 'misc-error
(lambda ()
(inferior-eval …))
…)
This will have to be adjusted. Does that work for you, Chris?
If you want to go fancy, you can implement a compatibility later, though
I’m not sure it’s worth it.
Eventually I’d like ‘&inferior-exception’ to include inferior stack
frames, though that’ll require changes to the REPL protocol.
Ludo’.
next prev parent reply other threads:[~2020-03-10 17:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 16:03 [bug#40016] [PATCH] inferior: Distinguish inferior exceptions Ludovic Courtès
2020-03-10 17:30 ` Ludovic Courtès [this message]
2020-03-11 0:09 ` Christopher Baines
2020-03-11 13:54 ` Ludovic Courtès
2020-03-12 12:43 ` bug#40016: " Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878sk8t8vr.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=40016@debbugs.gnu.org \
--cc=mail@cbaines.net \
/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/guix.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).