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

Message #22 received at 50629 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Gerd Möllmann <gerd.moellmann <at> gmail.com>
Cc: Mike Kupfer <mkupfer <at> alum.berkeley.edu>, 50629 <at> debbugs.gnu.org
Subject: Re: bug#50629: 28.0.50; hard to debug an uncaught error with ert
Date: Sat, 27 Aug 2022 15:52:45 +0200

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

> The backtrace we have already.  It's the "unreadable" stuff that ERT
> prints.

No, that's not the backtrace (that we're interested in).

With this example:

emake; ./src/emacs -Q -batch -l ert -eval '(ert-deftest f () (setq debug-on-error t) (defun foo () (bar)) (defun bar () (zot)) (should (equal 42 (foo))))' -f ert-run-tests-batch-and-exit

We'd like to see a backtrace that mentions that zot was called by bar,
and that bar was called by foo.  Instead we get:

Test f backtrace:
  signal(void-function (zot))
  apply(signal (void-function (zot)))
  (setq value-2 (apply fn-0 args-1))
  (unwind-protect (setq value-2 (apply fn-0 args-1)) (setq form-descri

Note that there's no mention of foo or bar.
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.