From: Ian Price <ianprice90@googlemail.com>
To: 13827@debbugs.gnu.org
Subject: bug#13827: faulty range check in bytevector accessor
Date: Wed, 27 Feb 2013 02:02:06 +0000 [thread overview]
Message-ID: <87liaay0o1.fsf@Kagami.home> (raw)
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)
Running this gives me a core dump. It happens for a wide range of values
that don't fit in 32 bits.
After some talk on #guile, Mark and I believe it comes down to the range
check in INTEGER_ACCESSOR_PROLOGUE in bytevectors.c
--
Ian Price -- shift-reset.com
"Programming is like pinball. The reward for doing it well is
the opportunity to do it again" - from "The Wizardy Compiled"
next reply other threads:[~2013-02-27 2:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 2:02 Ian Price [this message]
2013-02-27 2:30 ` bug#13827: faulty range check in bytevector accessor Mark H Weaver
2013-02-27 11:42 ` Ludovic Courtès
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=87liaay0o1.fsf@Kagami.home \
--to=ianprice90@googlemail.com \
--cc=13827@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).