From: Yuval Langer <yuval.langer@gmail.com>
To: 68362@debbugs.gnu.org
Subject: bug#68362: Wrong Guile version and a new error message
Date: Wed, 10 Jan 2024 06:24:34 +0200 [thread overview]
Message-ID: <CAK0OjG0S6xJymfbK_L5Go71hiLtHtH0vrak4fzLB+igNVT11FA@mail.gmail.com> (raw)
In-Reply-To: <CAK0OjG3As1+8fzPc5Q9Qme-TMCWHADXtdVA=Xic1d9pee-nm2g@mail.gmail.com>
Sorry,
I have provided the wrong version number used to produce the
segmentation fault. The true version is:
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.
as that is the one specified in ./rsv2scm's shebang.
Using the Guix version:
$ printf "\xfe" | guile -L . -e main -s rsv2scm
I get the following error:
Backtrace:
In ice-9/boot-9.scm:
1752:10 7 (with-exception-handler _ _ #:unwind? _ # _)
In unknown file:
6 (apply-smob/0 #<thunk 7fcdb7dbc300>)
In ice-9/boot-9.scm:
724:2 5 (call-with-prompt _ _ #<procedure default-prompt-handle…>)
In ice-9/eval.scm:
619:8 4 (_ #(#(#<directory (guile-user) 7fcdb7dbfc80>)))
In rsv2scm:
13:12 3 (main _)
In rsv/arbitrary-null.scm:
144:23 2 (rsv->scm #f #<input: file 0>)
116:11 1 (row->scm #f 0 #<input: file 0>)
84:4 0 (read-null-value _ _ _)
rsv/arbitrary-null.scm:84:4: In procedure read-null-value:
Wrong number of arguments to 254
The byte value being piped into guile is 254. Weird.
Thank you,
Yuval Langer.
prev parent reply other threads:[~2024-01-10 4:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 4:12 bug#68362: Segmentation fault when a procedure is called with no arguments Yuval Langer
2024-01-10 4:24 ` Yuval Langer [this message]
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=CAK0OjG0S6xJymfbK_L5Go71hiLtHtH0vrak4fzLB+igNVT11FA@mail.gmail.com \
--to=yuval.langer@gmail.com \
--cc=68362@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).