From: Kevin Ryde <user42@zip.com.au>
Cc: bug-guile@gnu.org
Subject: Re: guile segfaults
Date: Wed, 07 Jan 2004 08:10:45 +1000 [thread overview]
Message-ID: <87n0909196.fsf@zip.com.au> (raw)
In-Reply-To: 200401050401.i0541pWR002199@pc18.math.umbc.edu
[-- Attachment #1: Type: text/plain, Size: 224 bytes --]
"Rouben Rostamian" <rostamian@umbc.edu> writes:
>
> Guile segfaults when given the following code:
>
> (define a (make-uniform-array 1/3 3 3))
> (uniform-array-set1! a 5.0 (cons 0 0))
Thanks, a dodgy argument check.
[-- Attachment #2: unif.c.aind.diff --]
[-- Type: text/plain, Size: 357 bytes --]
--- unif.c.~1.137.~ 2003-09-13 09:34:18.000000000 +1000
+++ unif.c 2004-01-06 15:34:23.000000000 +1000
@@ -473,7 +473,7 @@
scm_error_num_args_subr (what);
return pos + (SCM_INUM (args) - s->lbnd) * (s->inc);
}
- while (k && !SCM_NULLP (args))
+ while (k && SCM_CONSP (args))
{
ind = SCM_CAR (args);
args = SCM_CDR (args);
[-- Attachment #3: Type: text/plain, Size: 136 bytes --]
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
prev parent reply other threads:[~2004-01-06 22:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 4:01 guile segfaults Rouben Rostamian
2004-01-06 22:10 ` Kevin Ryde [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=87n0909196.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=bug-guile@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).