From: Sascha Ziemann <ceving@gmail.com>
To: 60522@debbugs.gnu.org
Subject: bug#60522: make-vector takes 100% cpu if called without argument in the REPL
Date: Tue, 3 Jan 2023 17:57:19 +0100 [thread overview]
Message-ID: <CAGUt3y7pazQ02oku5gGLgFrFu4s2dRGLk3NMk2ADur8y6jwfbA@mail.gmail.com> (raw)
The following throws an error:
guile -c '(make-vector)'
But the evaluation of '(make-vector)' in the REPL generats just a warning:
;;; <stdin>:1:0: warning: possibly wrong number of arguments to `make-vector'
and seems to enter an endless loop afterwards.
Environment:
$ guile --version
guile (GNU Guile) 3.0.5
Packaged by Debian (3.0.5-deb+3.0.5-4)
Copyright (C) 2021 Free Software Foundation, Inc.
License LGPLv3+: GNU LGPL 3 or later <http://gnu.org/licenses/lgpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
$ uname -a
Linux l2108 5.10.0-20-amd64 #1 SMP Debian 5.10.158-2 (2022-12-13)
x86_64 GNU/Linux
next reply other threads:[~2023-01-03 16:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 16:57 Sascha Ziemann [this message]
2023-01-03 19:08 ` bug#60522: make-vector takes 100% cpu if called without argument in the REPL tomas
2023-01-16 14:36 ` Ludovic Courtès
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGUt3y7pazQ02oku5gGLgFrFu4s2dRGLk3NMk2ADur8y6jwfbA@mail.gmail.com \
--to=ceving@gmail.com \
--cc=60522@debbugs.gnu.org \
/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.
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).