[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#13827: faulty range check in bytevector accessor
From: |
Ludovic Courtès |
Subject: |
bug#13827: faulty range check in bytevector accessor |
Date: |
Wed, 27 Feb 2013 12:42:50 +0100 |
User-agent: |
Gnus/5.130005 (Ma Gnus v0.5) Emacs/24.2 (gnu/linux) |
Ian Price <address@hidden> 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’.