From: Marius Vollmer <mvo@zagadka.de>
Cc: bug-guile@gnu.org, jantien@xs4all.nl, guile-devel@gnu.org,
fodber@interware.hu
Subject: Re: Serious GC bug in GUILE 1.6 CVS
Date: Thu, 09 Sep 2004 01:27:51 +0200 [thread overview]
Message-ID: <87zn4049zc.fsf@zagadka.ping.de> (raw)
In-Reply-To: <16703.37535.594397.357127@byrd.xs4all.nl> (Han-Wen Nienhuys's message of "Thu, 9 Sep 2004 01:15:43 +0200")
Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
> Hmm... That's unfortunate. We have reports of GC flakiness with 1.6
> on Cygwin. This means that there's still another bug lurking.
Yes, the bug that I just fixed bites only with DEBUG_CELL_ACCESSES.
Your's must be something else.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2004-09-08 23:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-17 21:27 Serious GC bug in GUILE 1.6 CVS Han-Wen Nienhuys
2004-09-07 15:45 ` Marius Vollmer
2004-09-08 23:15 ` Han-Wen Nienhuys
2004-09-08 23:27 ` Marius Vollmer [this message]
2004-09-09 22:32 ` Neil Jerram
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=87zn4049zc.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
--cc=bug-guile@gnu.org \
--cc=fodber@interware.hu \
--cc=guile-devel@gnu.org \
--cc=jantien@xs4all.nl \
/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).