From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: bug-guile@gnu.org
Subject: Re: possible gc/weak hash table bug
Date: Fri, 25 Mar 2011 10:23:24 +0100 [thread overview]
Message-ID: <m3y643h7ub.fsf@unquote.localdomain> (raw)
In-Reply-To: <87r5a4odeg.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 18 Mar 2011 12:51:03 +0100")
On Fri 18 Mar 2011 12:51, ludo@gnu.org (Ludovic Courtès) writes:
> michaelawells <michaelawells@gmail.com> writes:
>
>>> size_t len = SCM_HASHTABLE_N_ITEMS (table);
>>>
>>> while (k--)
>>> {
>>> size_t removed;
>>> SCM alist = SCM_SIMPLE_VECTOR_REF (buckets, k);
>>> alist = scm_fixup_weak_alist (alist, &removed); <<<**** FAILS HERE
>>> assert (removed <= len);
>
> Andy, isn’t this assertion bogus since N_ITEMS is updated lazily and
> thus may not correspond to the current number of items?
I don't think so; this is the procedure that is doing that lazy sweep.
Michael, how are you using this hash table? Are you accessing it from
different pthreads? What version of libgc are you using? (Did you
enable parallel collection?)
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-03-25 9:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A7D64DB3-0467-49D7-9D4E-6E9634782F90@gmail.com>
[not found] ` <m3mxku13rd.fsf@unquote.localdomain>
2011-03-18 0:09 ` possible gc/weak hash table bug michaelawells
2011-03-18 3:31 ` michaelawells
2011-03-18 11:51 ` Ludovic Courtès
2011-03-25 9:23 ` Andy Wingo [this message]
2011-03-25 21:48 michaelawells
2011-03-26 1:15 ` michaelawells
2011-04-28 9:52 ` 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=m3y643h7ub.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-guile@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).