From: "Ludovic Courtès" <ludo@gnu.org>
To: Rob Browning <rlb@defaultvalue.org>
Cc: 39586@debbugs.gnu.org
Subject: bug#39586: pfds 0.3 hamt-fold crashes with guile-2.0 and guile-3.0
Date: Sat, 21 Mar 2020 18:58:41 +0100 [thread overview]
Message-ID: <87v9mxy4ha.fsf@gnu.org> (raw)
In-Reply-To: <87v9obx9k2.fsf@trouble.defaultvalue.org> (Rob Browning's message of "Thu, 13 Feb 2020 00:53:17 -0600")
Hi Rob,
Rob Browning <rlb@defaultvalue.org> skribis:
> With the current pdfs (https://github.com/ijp/pfds
> 454033f82dac7c0b0ea9e84eed1e8ed316487c78), the code below halts on an
> rnrs record assertion failure with both guile-2.2 and guile-3.0, and I'm
> wondering if I'm doing something wrong, if it might be a guile bug, or
> if it's more likely an issue with pfds.
>
> (use-modules
> ((pfds hamts) #:prefix hamts/)
> ((srfi srfi-69) #:prefix hash/))
>
> (define x (hamts/hamt-set
> (hamts/hamt-set
> (hamts/hamt-set
> (hamts/make-hamt hash/hash eqv?)
> #:x 1)
> #:y 2)
> #:z 3))
>
> (hamts/hamt-fold (lambda (k v result) result)
>
> It looks like the crash is in (rnrs records procedural) here:
>
> (if (and parent (struct-ref parent rtd-index-sealed?))
> (r6rs-raise (make-assertion-violation)))
Do you think you could boil it down to a test that does not rely on pfds?
Thanks,
Ludo’.
prev parent reply other threads:[~2020-03-21 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 6:53 bug#39586: pfds 0.3 hamt-fold crashes with guile-2.0 and guile-3.0 Rob Browning
2020-03-21 17:58 ` Ludovic Courtès [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=87v9mxy4ha.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=39586@debbugs.gnu.org \
--cc=rlb@defaultvalue.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).