bug#50629: 28.0.50; hard to debug an uncaught error with ert

[Lars Ingebrigtsen <larsi@gnus.org>]

Gerd Möllmann <gerd.moellmann@gmail.com> writes:

>> Anybody more familiar with ert.el know how this can be achieved?
>
> Not exactly this, I guess, but maybe as source of an idea?

[...]

> +                   (ert--pp-with-indentation-and-newline
> +                    (ert-test-result-with-condition-should-forms result))
>                     (ert--pp-with-indentation-and-newline
>                      (ert-test-result-with-condition-condition result)))
>                   (goto-char (1- (point-max)))
>
> leads to output
>
> Test f condition:
>     (((should
>        (equal 42
> 	      (foo)))
>       :form
>       (signal void-function
> 	      (bar))))
> (void-function bar)

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.