From: Andy Wingo <wingo@pobox.com>
To: Mark H Weaver <mhw@netris.org>
Cc: Cole Minaar <cole.minaar@concurrent.co.za>, 16641-done@debbugs.gnu.org
Subject: bug#16641: Assert triggered (hashtab.c:137) - Guile-2.0.9
Date: Tue, 21 Jun 2016 14:58:17 +0200 [thread overview]
Message-ID: <87inx2zok6.fsf@pobox.com> (raw)
In-Reply-To: <87k3d9y2m5.fsf@netris.org> (Mark H. Weaver's message of "Wed, 05 Feb 2014 10:56:50 -0500")
On Wed 05 Feb 2014 16:56, Mark H Weaver <mhw@netris.org> writes:
> Also: this is on Solaris 10u10. Cole mentioned that on IRC.
On the one hand I don't understand how this can happen. On the other, I
unfortunately don't have faith in the buckets-and-chains weak table
implementation in 2.0; it usually works but it's gnarly and is a
threading nightmare, and accesses disappearing links outside the alloc
lock. See for example:
http://article.gmane.org/gmane.comp.programming.garbage-collection.boehmgc/4789
In 2.2 the weak table is rewritten to not require the "vacuum" phase and
to be threadsafe. That was my best effort at fixing this bug but I
couldn't do it with some of the constraints in 2.0. For that reason I
am closing this one but feel free to re-open it if you find available
hackpower to work towards a solution for 2.0.
Andy
prev parent reply other threads:[~2016-06-21 12:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1490214189.217964.1391502321350.JavaMail.zimbra@concurrent.co.za>
2014-02-04 8:43 ` bug#16641: Assert triggered (hashtab.c:137) - Guile-2.0.9 Cole Minaar
2014-02-04 9:41 ` Cole Minaar
2014-02-05 15:56 ` Mark H Weaver
2016-06-21 12:58 ` Andy Wingo [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=87inx2zok6.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=16641-done@debbugs.gnu.org \
--cc=cole.minaar@concurrent.co.za \
--cc=mhw@netris.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).