From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Mike Kupfer <mkupfer@alum.berkeley.edu>, 50629@debbugs.gnu.org
Subject: bug#50629: 28.0.50; hard to debug an uncaught error with ert
Date: Sat, 27 Aug 2022 15:44:12 +0200 [thread overview]
Message-ID: <m2ler94x8z.fsf@Mini.fritz.box> (raw)
In-Reply-To: <871qt1aklk.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 27 Aug 2022 15:20:55 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Hm, yes... But it'd be really useful to have the complete backtrace
> instead of just the signal form, because the errors that this would be
> most helpful for are often way down in the call stack.
The backtrace we have already. It's the "unreadable" stuff that ERT
prints. It's hard to make sense of because of the macrology involved.
If you macroexpand the ert-deftest form that Mike provided, you'll see
what I mean.
And that's also what one will see in a debugger. (There's an
ert-debug-on-error, BTW. I think someone asked.)
Don't know, maybe you could change ert-deftest to expand into something
more readable?
next prev parent reply other threads:[~2022-08-27 13:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 23:28 bug#50629: 28.0.50; hard to debug an uncaught error with ert Mike Kupfer
2022-08-26 11:41 ` Lars Ingebrigtsen
2022-08-26 13:52 ` Gerd Möllmann
2022-08-27 13:20 ` Lars Ingebrigtsen
2022-08-27 13:44 ` Gerd Möllmann [this message]
2022-08-27 13:52 ` Lars Ingebrigtsen
2022-08-27 14:06 ` Gerd Möllmann
2022-08-27 14:29 ` Lars Ingebrigtsen
2022-08-27 14:38 ` Mike Kupfer
2022-08-27 14:40 ` Lars Ingebrigtsen
2022-08-27 15:13 ` Gerd Möllmann
2022-08-28 1:21 ` Ihor Radchenko
2022-08-28 9:27 ` Gerd Möllmann
2022-08-28 10:03 ` Lars Ingebrigtsen
2022-08-28 10:31 ` Gerd Möllmann
2022-08-28 10:43 ` Gerd Möllmann
2022-08-28 12:25 ` Gerd Möllmann
2022-08-29 14:46 ` Lars Ingebrigtsen
2022-08-29 15:20 ` Gerd Möllmann
2022-08-29 15:28 ` Lars Ingebrigtsen
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=m2ler94x8z.fsf@Mini.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=50629@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mkupfer@alum.berkeley.edu \
/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).