From: Rob Browning <rlb@defaultvalue.org>
To: Andy Wingo <wingo@pobox.com>
Cc: bug-guile@gnu.org
Subject: Re: gc.test hangs with Guile 2.0.0 and Debian libgc 7.1-4
Date: Sun, 20 Feb 2011 16:07:58 -0600 [thread overview]
Message-ID: <8762sexsu9.fsf@raven.defaultvalue.org> (raw)
In-Reply-To: <m37hcuz8x0.fsf@unquote.localdomain> (Andy Wingo's message of "Sun, 20 Feb 2011 22:35:23 +0100")
Andy Wingo <wingo@pobox.com> writes:
> Not sure. Could it be the same as
> http://article.gmane.org/gmane.lisp.guile.bugs/5007/match=threads+test ?
I'll try libgc CVS when I get a chance. If that turns out to be the
problem, I might see if I can track down a suitable patch for 7.2. Any
idea what the libgc release plans look like?
Thanks
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
prev parent reply other threads:[~2011-02-20 22:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-20 18:57 gc.test hangs with Guile 2.0.0 and Debian libgc 7.1-4 Rob Browning
2011-02-20 21:35 ` Andy Wingo
2011-02-20 22:07 ` Rob Browning [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=8762sexsu9.fsf@raven.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=bug-guile@gnu.org \
--cc=wingo@pobox.com \
/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).