From: <tomas@tuxteam.de>
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 20:08:40 +0100 [thread overview]
Message-ID: <Y7R9OKi2anHt+2go@tuxteam.de> (raw)
In-Reply-To: <CAGUt3y7pazQ02oku5gGLgFrFu4s2dRGLk3NMk2ADur8y6jwfbA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 457 bytes --]
On Tue, Jan 03, 2023 at 05:57:19PM +0100, Sascha Ziemann wrote:
> 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.
Can confirm for 3.0.8.57-bc3b1. It actually eats CPU, can be interrupted
with c-C.
Cheers
--
t
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2023-01-03 19:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 16:57 bug#60522: make-vector takes 100% cpu if called without argument in the REPL Sascha Ziemann
2023-01-03 19:08 ` tomas [this message]
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=Y7R9OKi2anHt+2go@tuxteam.de \
--to=tomas@tuxteam.de \
--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).