From: "Julian Graham" <joolean@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: segfault in SRFI-1 partition on non-list input
Date: Mon, 28 Apr 2008 09:41:26 -0400 [thread overview]
Message-ID: <2bc5f8210804280641r1c51a266x52883da55d882a3b@mail.gmail.com> (raw)
In-Reply-To: <87bq3ul6yd.fsf@gnu.org>
> The probably is that `SCM_VALIDATE_LIST' uses `scm_ilength ()', which
> attempts to traverse the list it's given. Thus, it is undesirable to
> use it here (and in many other places actually).
>
> Instead, I propose the following patch, which doesn't add any list
> traversal but doesn't catch circular lists. What do you think?
Oh, yeah, that's fine -- sorry, didn't realize that was the behavior
of SCM_VALIDATE_LIST. Just as long as it doesn't segfault any more,
I'm happy.
Regards,
Julian
next prev parent reply other threads:[~2008-04-28 13:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 4:37 segfault in SRFI-1 partition on non-list input Julian Graham
2008-04-28 8:27 ` Ludovic Courtès
2008-04-28 8:31 ` Ludovic Courtès
2008-04-28 13:41 ` Julian Graham [this message]
2008-04-28 15:28 ` Ludovic Courtès
2008-04-30 3:40 ` Julian Graham
2008-04-30 7:28 ` Ludovic Courtès
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=2bc5f8210804280641r1c51a266x52883da55d882a3b@mail.gmail.com \
--to=joolean@gmail.com \
--cc=guile-devel@gnu.org \
--cc=ludo@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).