From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Mike Kupfer <mkupfer@alum.berkeley.edu>,
Ihor Radchenko <yantar92@gmail.com>,
50629@debbugs.gnu.org
Subject: bug#50629: 28.0.50; hard to debug an uncaught error with ert
Date: Sun, 28 Aug 2022 12:31:20 +0200 [thread overview]
Message-ID: <m27d2s8xs7.fsf@Mini.fritz.box> (raw)
In-Reply-To: <875yicptwk.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 28 Aug 2022 12:03:07 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Gerd Möllmann <gerd.moellmann@gmail.com> writes:
>
>> Interestingly with condition-case-unless I get one less error with make
>> check:
>
> Are you sure you removed all the .elc files under test first? Since
> this is a change in an ert macro, you have to do that to get meaningful
> results.
I did a make -C test clean, but now that you say it I checked, and make
clean does not remove elcs. Which I personally find surprising.
I'll check with elcs removed between runs later.
> Anyway, that condition-case is presumably there to allow checking for
> failures? I.e., the :expected stuff.
Ok.
> Instead of altering removing the condition-case there, wouldn't it be
> possible to output the backtrace explicitly in the handler?
You mean the signal-hook-function? It is invoked, so one can do
something there. If it would invoke the debugger, that would also work,
I think, but I haven't checked. Directly outputting something there is
probably not a good idea. If anything it should record the backtrace in
ERT result structs, like ERT's debugger function.
next prev parent reply other threads:[~2022-08-28 10:31 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
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 [this message]
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=m27d2s8xs7.fsf@Mini.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=50629@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mkupfer@alum.berkeley.edu \
--cc=yantar92@gmail.com \
/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).