From: Alan Mackenzie <acm@muc.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>,
"Mattias Engdegård" <mattiase@acm.org>,
58601@debbugs.gnu.org
Subject: bug#58601: 29.0.50; Infinite loop in byte-compile--first-symbol-with-pos
Date: Wed, 19 Oct 2022 08:52:10 +0000 [thread overview]
Message-ID: <Y0+6ut4tMTyG0j4u@ACM> (raw)
In-Reply-To: <jwv1qr5hris.fsf-monnier+emacs@gnu.org>
On Tue, Oct 18, 2022 at 15:19:35 -0400, Stefan Monnier wrote:
> >> That's not the problem, because it's just for illustrative purposes.
> >> Instead of 'arg' being passed unchanged as the FORM argument, it could
> >> just as well have been `(my-frobnicate ,arg).
> > That would not loop, since there is a symbol with position there.
> BTE, the real-world use case is a compiler macro which takes the list of
> args and tucks the name of another function in front. So the generated
> code, passed to `macroexp-warn-and-return` has the shape
> (somefun somearg1 somearg2)
> where `somefun` does *not* come from the source but from the
> compiler-macro instead and hence doesn't have any sympos, and then
> `somearg1` was an expression of the form
> (quote #1=(1 2 3 . #1#))
> So, there was no cycle in the code part, the cycle is only inside the
> data embedded in the code.
I think somebody who writes something like that _deserves_ to go into an
infinite loop. Have you ever seen anything at all like this in real
life?
You have fixed this "problem" by arbitrarily limiting the size of valid
form stacks that can be searched, and the depth to which they can be
searched. This limit, 10, seems too small. There can easily be form
stacks with more than 10 elements. Do you have any objection if I
change that 10 to something closer to infinity? Something which will
encompass any form stack likely to be encountered in practice? I would
suggest the number 300.
> Stefan
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2022-10-19 8:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 23:24 bug#58601: 29.0.50; Infinite loop in byte-compile--first-symbol-with-pos Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-18 14:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-18 16:33 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-18 19:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-18 15:01 ` Alan Mackenzie
2022-10-18 16:18 ` dick
2022-10-18 16:34 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-18 17:06 ` Alan Mackenzie
2022-10-18 17:39 ` dick
2022-10-18 19:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-19 8:52 ` Alan Mackenzie [this message]
2022-10-19 12:48 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-21 10:57 ` Mattias Engdegård
2022-10-21 10:47 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-21 10:47 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=Y0+6ut4tMTyG0j4u@ACM \
--to=acm@muc.de \
--cc=58601@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=mattiase@acm.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.