unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: "Mattias Engdegård" <mattias.engdegard@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: The poor quality of Emacs's backtraces
Date: Fri, 14 Jul 2023 20:51:50 +0000	[thread overview]
Message-ID: <ZLG1Zk07Sv1wQ5on@ACM> (raw)
In-Reply-To: <909FC7C1-5473-4746-97E4-B067E6C2B271@gmail.com>

Hello, Mattias.

On Fri, Jul 14, 2023 at 20:06:02 +0200, Mattias Engdegård wrote:
> 14 juli 2023 kl. 15.07 skrev Alan Mackenzie <acm@muc.de>:

> > There are only 1,728 occurrences of CHECK_* in the Emacs C sources.
> > Much of the amendment could be automated.

> No, we had better be careful here -- don't want to make anything slower.

Aren't we always careful?  I wasn't intending to make anything slower
(except, marginally, the handling of errors).

> > Yesterday evening, the identity of {comp-spill-lap-function} was
> > very helpful in locating the buggy source.

> That was yesterday. Today you wouldn't need it, because nth now
> appears in the backtrace (well, most of the time).

That's a rather strange notion.  Whether it's "needed" or not, it's
undeniably helpful.  I think you agreed yesterday with my basic tenet,
that Emacs backtraces are of poor quality.  This is one way that quality
can be raised.

> > Do you have any alternative mechanism in mind for identifying anonymous
> > functions in backtraces?

> I disagree with the idea of that somehow being a requirement.

Why?  Are you working on anything which could remotely be considered a
competitor for this facility; something you suggested yesterday might be
the case?

I have working code implementing the putting of this extra information
into backtraces.  Again, why do you regard this as a negative feature?

-- 
Alan Mackenzie (Nuremberg, Germany).



  reply	other threads:[~2023-07-14 20:51 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
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 [this message]
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=ZLG1Zk07Sv1wQ5on@ACM \
    --to=acm@muc.de \
    --cc=emacs-devel@gnu.org \
    --cc=mattias.engdegard@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).