From: ludo@gnu.org (Ludovic Courtès)
To: Ian Price <ianprice90@googlemail.com>
Cc: 13827@debbugs.gnu.org
Subject: bug#13827: faulty range check in bytevector accessor
Date: Wed, 27 Feb 2013 12:42:50 +0100 [thread overview]
Message-ID: <87r4k2x9s5.fsf@gnu.org> (raw)
In-Reply-To: <87liaay0o1.fsf@Kagami.home> (Ian Price's message of "Wed, 27 Feb 2013 02:02:06 +0000")
Ian Price <ianprice90@googlemail.com> skribis:
> Branch: master
> Commit: 9b977c836bf147d386944c401113aba32776fa68
> System: 32 bit x86 Fedora 16
>
> (use-modules (rnrs bytevectors))
> (define not-32-bit (expt 2 32))
> (define bv (make-bytevector 4))
> (bytevector-u32-set! bv 0 not-32-bit (endianness big))
> (pk bv)
FWIW, with 2.0.7+ on x86_64-linux-gnu, with GMP 5.1.0:
--8<---------------cut here---------------start------------->8---
scheme@(guile-user)> (use-modules (rnrs bytevectors))
scheme@(guile-user)> (define not-32-bit (expt 2 32))
scheme@(guile-user)> (define bv (make-bytevector 4))
scheme@(guile-user)> (bytevector-u32-set! bv 0 not-32-bit (endianness big))
<unnamed port>:4:0: In procedure #<procedure 1b1bf00 at <current input>:4:0 ()>:
<unnamed port>:4:0: In procedure bytevector-u32-set!: Value out of range: 4294967296
Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue.
--8<---------------cut here---------------end--------------->8---
As Mark pointed out, it could be due to the GMP version you’re using.
Could you check that?
TIA,
Ludo’.
next prev parent reply other threads:[~2013-02-27 11:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 2:02 bug#13827: faulty range check in bytevector accessor Ian Price
2013-02-27 2:30 ` Mark H Weaver
2013-02-27 11:42 ` Ludovic Courtès [this message]
2013-02-28 1:38 ` Mark H Weaver
2013-02-28 20:20 ` Ian Price
2013-03-13 12:55 ` Andy Wingo
2013-03-13 14:37 ` Andy Wingo
2014-07-28 14:35 ` Ben Rocer
2016-06-20 15:16 ` Andy Wingo
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=87r4k2x9s5.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=13827@debbugs.gnu.org \
--cc=ianprice90@googlemail.com \
/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).