From: Alan Mackenzie <acm@muc.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: acm@muc.de, Eli Zaretskii <eliz@gnu.org>,
Protesilaos Stavrou <info@protesilaos.com>,
55414@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#55414: 29.0.50; Byte compilation error for the modus-themes
Date: Fri, 27 May 2022 09:52:30 +0000 [thread overview]
Message-ID: <YpCfXnmWXrEB6u2v@ACM> (raw)
In-Reply-To: <875ylscxre.fsf@gnus.org>
Hello, Lars.
On Thu, May 26, 2022 at 13:57:09 +0200, Lars Ingebrigtsen wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
> > Lars, is it just me, or are you also concerned by a large increase in
> > the default values of these variables?
> I'm not really that concerned in general, but in this case, the entire
> problem ....
Which problem would that be, exactly? If it's the failure of
modus-themes to compile without causing a stack overflow error, then ...
> .... is apparently due to one function --
> byte-compile--first-symbol-with-pos -- that's very recursive.
No, no, no, no. byte-compile--first-symbol-with-pos is NOT the cause of
the stack overflow - it's part of the handling of that stack overflow,
and unfortunately causes a second stack overflow. Having examined
Prot's backtraces (around 16th May), I explained this in my post of
2022-05-16 as follows:
#########################################################################
Looking a bit more carefully at the backtrace, it's evident there were
two lisp eval depth overflows. The first was in the compilation of the
library, where a condition-case was used to discard the diagnostic data
(I hate it when this is done). This was in the macro
displaying-byte-compile-warnings in .../lisp/emacs-lisp/bytecomp.el.
This failure then called the byte compiler error routines, which caused
the second overflow, in byte-compile--first-symbol-with-pos.
This second overflow is "only just" happening - another few spare slots,
and it would have succeeded; at least on this particular part of the
program structure.
#########################################################################
> It could be rewritten to not be recursive, and these problems would go
> away (which we've seen in many contexts now), if I understand
> correctly.
You're saying byte-compile--first-symbol-with-pos could be reformulated
to be non-recursive, I think. I don't understand that. It is a
function working on an arbitrary tree structure. Such functions are
always coded using recursion, aren't they? What am I missing here?
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2022-05-27 9:52 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 18:07 bug#55414: 29.0.50; Byte compilation error for the modus-themes Protesilaos Stavrou
2022-05-15 13:45 ` Lars Ingebrigtsen
[not found] ` <87lev296hl.fsf@protesilaos.com>
2022-05-15 15:16 ` Lars Ingebrigtsen
2022-05-16 7:58 ` Alan Mackenzie
2022-05-16 8:21 ` Protesilaos Stavrou
2022-05-16 11:15 ` Eli Zaretskii
2022-05-16 12:03 ` Alan Mackenzie
2022-05-16 12:26 ` Eli Zaretskii
2022-05-16 13:48 ` Alan Mackenzie
2022-05-16 13:56 ` Eli Zaretskii
2022-05-16 14:52 ` Protesilaos Stavrou
2022-05-16 15:56 ` Eli Zaretskii
2022-05-22 13:10 ` Alan Mackenzie
2022-05-22 13:25 ` Eli Zaretskii
2022-05-23 3:51 ` Protesilaos Stavrou
2022-05-23 10:57 ` Eli Zaretskii
2022-05-24 4:37 ` Protesilaos Stavrou
2022-05-24 11:09 ` Eli Zaretskii
2022-05-25 3:24 ` Protesilaos Stavrou
2022-05-25 13:12 ` Eli Zaretskii
2022-05-26 5:55 ` Protesilaos Stavrou
2022-05-26 11:32 ` Eli Zaretskii
2022-05-26 11:57 ` Lars Ingebrigtsen
2022-05-26 12:59 ` Eli Zaretskii
2022-05-26 15:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-26 15:42 ` Protesilaos Stavrou
2022-05-27 9:52 ` Alan Mackenzie [this message]
2022-05-27 10:25 ` Lars Ingebrigtsen
2022-05-26 16:02 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-26 15:30 ` Mattias Engdegård
2022-05-27 9:03 ` Mattias Engdegård
2022-05-27 10:23 ` Lars Ingebrigtsen
2022-05-27 10:39 ` Protesilaos Stavrou
2022-05-27 10:42 ` Lars Ingebrigtsen
2022-05-27 11:32 ` Alan Mackenzie
2022-05-27 11:52 ` Lars Ingebrigtsen
2022-05-27 13:42 ` Alan Mackenzie
2022-05-27 13:50 ` Lars Ingebrigtsen
2022-05-28 23:13 ` Richard Stallman
2022-05-27 12:15 ` Protesilaos Stavrou
2022-05-27 13:59 ` Alan Mackenzie
2022-05-27 16:53 ` Mattias Engdegård
2022-05-27 18:24 ` Alan Mackenzie
2022-05-29 9:18 ` Mattias Engdegård
2022-05-29 13:38 ` Alan Mackenzie
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YpCfXnmWXrEB6u2v@ACM \
--to=acm@muc.de \
--cc=55414@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=info@protesilaos.com \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.