unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: "Mattias Engdegård" <mattias.engdegard@gmail.com>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: The poor quality of Emacs's backtraces
Date: Tue, 18 Jul 2023 13:57:51 +0000	[thread overview]
Message-ID: <ZLaaXzWt-JkNv0ND@ACM> (raw)
In-Reply-To: <87mszt305f.fsf@localhost>

Hello, Ihor.

On Tue, Jul 18, 2023 at 11:54:36 +0000, Ihor Radchenko wrote:
> Alan Mackenzie <acm@muc.de> writes:

> >> This is curious. I tried to branch and got several native-comp errors:

> > Thanks for actually trying this out!

> > One thing I forgot to say: you need to run make bootstrap, since the
> > format of some internal structures is being changed.  If you didn't do
> > this, please try it.  If you did run make bootstrap, please let me know,
> > then I will take a closer look at your backtraces.  Thanks!

> I did. Now, to be sure, I also did make extraclean; ./autogen...;
> ./configure...; make boostrap
> And then also removed eln-cache dir.

> Things changed somewhat:

> In toplevel form:
> eval-sexp-fu.el:121:2: Warning: Package cl is deprecated
> eval-sexp-fu.el:145:2: Warning: custom-declare-variable `eval-sexp-fu-flash-error-face' docstring wider than 80 characters
> /home/yantar92/.emacs.d/straight/build/eval-sexp-fu/eval-sexp-fu.el: Error: Wrong type argument listp

> /home/yantar92/.emacs.d/straight/build/helm-dash/helm-dash.el: Error: Wrong type argument listp

> No backtrace this time.

Excellent!

> Not sure if it is related to the branch.

I've not been able to install helm successfully on standard Emacs, but
those "error messages" illustrate to some extent the problem I'm trying
to solve.  They give no location, beyond a file name, for the problem;
they don't say what isn't a list, and don't say what primitive detected
its not being a list.

If you know helm well, can you say whether or not it handles function
structure explicitly?  Doing things like assuming the element of a
lambda form following 'lambda is the parameter list?  This might be the
cause of the problem.

> -- 
> 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).



  reply	other threads:[~2023-07-18 13:57 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
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 [this message]
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=ZLaaXzWt-JkNv0ND@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).