GNU bug report logs - #50629
28.0.50; hard to debug an uncaught error with ert

Previous Next

Package: emacs;

Reported by: Mike Kupfer <mkupfer <at> alum.berkeley.edu>

Date: Thu, 16 Sep 2021 23:29:02 UTC

Severity: normal

Merged with 58941

Found in versions 28.0.50, 28.1.90

Full log

View this message in rfc822 format

From: Gerd Möllmann <gerd.moellmann <at> gmail.com>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: Mike Kupfer <mkupfer <at> alum.berkeley.edu>, 50629 <at> 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

Lars Ingebrigtsen <larsi <at> 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?
This bug report was last modified 2 years and 227 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.