From: Greg Troxel <gdt@ir.bbn.com>
Cc: guile-user@gnu.org
Subject: Re: out-of-order GC
Date: 30 Dec 2002 08:36:17 -0500 [thread overview]
Message-ID: <rmiptrjljce.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: Egil Moeller's message of "Sun, 29 Dec 2002 17:36:28 +0100 (CET)"
It sounds like your problem is that the transaction SMOB is holding a
reference to the connection SMOB, but that the GC system is not aware
of this. The transaction SMOB's mark routine should return (or call
mark on) the connection SMOB. Thus, until all the transaction SMOBs
are freed, the connection SMOB will still be in use.
Greg Troxel <gdt@ir.bbn.com>
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2002-12-30 13:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-29 16:36 out-of-order GC Egil Moeller
2002-12-30 13:36 ` Greg Troxel [this message]
2002-12-30 14:05 ` Egil Moeller
2002-12-31 3:06 ` Matt Hellige
2002-12-31 20:13 ` Neil Jerram
2003-01-01 10:57 ` Egil Moeller
2003-01-01 17:58 ` Neil Jerram
2003-01-01 21:22 ` Marius Vollmer
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=rmiptrjljce.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.com \
--cc=guile-user@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).