From: Alan Mackenzie <acm@muc.de>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: "Mattias Engdegård" <mattias.engdegard@gmail.com>, emacs-devel@gnu.org
Subject: Re: The poor quality of Emacs's backtraces
Date: Fri, 14 Jul 2023 10:58:28 +0000 [thread overview]
Message-ID: <ZLEqVNv6Guk19eZz@ACM> (raw)
In-Reply-To: <87h6q6j1gk.fsf@localhost>
Hello, Ihor and Mattias.
On Fri, Jul 14, 2023 at 09:18:19 +0000, Ihor Radchenko wrote:
> Mattias Engdegård <mattias.engdegard@gmail.com> writes:
> > 14 juli 2023 kl. 10.00 skrev Ihor Radchenko <yantar92@posteo.net>:
[ .... ]
> I am a bit confused.
> Aren't we talking about terminal output?
> >> Of course, the `condition-case' created by ERT will still be an issue.
> > Yes, and that was probably what really caused Alan's troubles. We could do something about that.
condition-case and backtrace mix very poorly. The problem is that, in
the event of an error, condition-case unwinds the stack _before_
executing its error handler. So the pertinent information is discarded
before backtrace gets evaluated.
As yet, I've only got vague notions as to how to solve this. But it
surely ought to be possible to amend condition-case, or create a variant
of condition-case, where the stack unwinding only occurs _after_
evaluating the error handler.
> I think that this problem was left unresolved due to lack of ideas:
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50629
That bug looks like just the same problems I'm having.
> --
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at <https://orgmode.org/>.
> Support Org development at <https://liberapay.com/org-mode>,
> or support my work at <https://liberapay.com/yantar92>
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2023-07-14 10:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 13:35 The poor quality of Emacs's backtraces Alan Mackenzie
2023-07-13 14:17 ` Christopher Dimech
2023-07-13 14:57 ` Mattias Engdegård
2023-07-14 8:00 ` Ihor Radchenko
2023-07-14 9:08 ` Mattias Engdegård
2023-07-14 9:18 ` Ihor Radchenko
2023-07-14 10:58 ` Alan Mackenzie [this message]
2023-07-14 10:56 ` Eli Zaretskii
2023-07-14 10:48 ` Alan Mackenzie
2023-07-14 12:35 ` Mattias Engdegård
2023-07-14 13:07 ` Alan Mackenzie
2023-07-14 18:06 ` Mattias Engdegård
2023-07-14 20:51 ` Alan Mackenzie
2023-07-17 15:52 ` Mattias Engdegård
2023-07-17 19:02 ` Alan Mackenzie
2023-07-17 19:50 ` Ihor Radchenko
2023-07-18 11:19 ` Alan Mackenzie
2023-07-18 11:54 ` Ihor Radchenko
2023-07-18 13:57 ` Alan Mackenzie
2023-07-19 8:05 ` Ihor Radchenko
2023-07-19 10:33 ` Mattias Engdegård
2023-07-19 15:45 ` Alan Mackenzie
2023-07-14 1:10 ` Michael Heerdegen
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=ZLEqVNv6Guk19eZz@ACM \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=mattias.engdegard@gmail.com \
--cc=yantar92@posteo.net \
/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).