From: Mikael Djurfeldt <mdjurfeldt@gmail.com>
Cc: Mikael Djurfeldt <djurfeldt@nada.kth.se>, guile-devel@gnu.org
Subject: Re: module GC bug
Date: Fri, 8 Jul 2005 11:24:50 +0200 [thread overview]
Message-ID: <66e540fe05070802241cbf85ad@mail.gmail.com> (raw)
In-Reply-To: <87fyuq1mrr.fsf@zagadka.de>
On 7/7/05, Marius Vollmer <mvo@zagadka.de> wrote:
> > I've fixed this by introducing a new function (eval-closure-module)
> > which returns the module of a closure via the eval-closure smob.
>
> I think the right fix is to change the weak hashtable marking
> algorithm to properly cope with circular references like this. I will
> try this and then come back to you. (I don't know how long this might
> take since the required changes look to be slightly non-trivial (but
> entirely possible).)
That would be good, because the current fix (which is already
committed to CVS HEAD, and which removes the setting of the
procedure-property) still leaves code in modules.c which expects the
procedure-property to be set. If Han-Wen's fix is to be kept, then
you should, at least, remove that code. The consequence is that it
will no longer be possible to lookup the module of the eval closure
for any kind of closures except the standard ones (which are
implemented as a smob).
M
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-07-08 9:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-09 23:32 module GC bug Han-Wen Nienhuys
2005-06-10 6:32 ` Neil Jerram
2005-06-10 11:48 ` Han-Wen Nienhuys
2005-06-19 13:32 ` Han-Wen Nienhuys
2005-06-19 17:33 ` Rob Browning
2005-07-07 18:48 ` Marius Vollmer
2005-06-24 17:50 ` Han-Wen Nienhuys
2005-07-07 18:42 ` Marius Vollmer
2005-07-08 9:24 ` Mikael Djurfeldt [this message]
2005-07-09 8:28 ` Han-Wen Nienhuys
2005-07-09 19:28 ` Mikael Djurfeldt
2005-07-09 23:25 ` Han-Wen Nienhuys
2005-07-10 8:16 ` Mikael Djurfeldt
2005-07-09 23:32 ` Han-Wen Nienhuys
2005-07-10 8:17 ` Mikael Djurfeldt
2005-07-08 21:43 ` Han-Wen Nienhuys
2005-07-13 21:02 ` Marius Vollmer
2005-07-13 22:19 ` Han-Wen Nienhuys
2005-07-16 18:57 ` Marius Vollmer
2005-07-17 18:50 ` Han-Wen Nienhuys
2005-07-17 20:44 ` Marius Vollmer
2005-07-18 13:43 ` Han-Wen Nienhuys
2005-08-01 0:20 ` Marius Vollmer
2005-08-01 11:04 ` Han-Wen Nienhuys
2005-08-10 22:29 ` Marius Vollmer
2005-08-15 23:57 ` Rob Browning
2005-08-16 0:10 ` Marius Vollmer
2005-08-16 0:16 ` Rob Browning
2005-08-28 23:31 ` Han-Wen Nienhuys
[not found] ` <42EE63F9.4080102@xs4all.nl>
2005-08-02 19:14 ` Marius Vollmer
[not found] ` <42F1DF3E.70204@xs4all.nl>
2005-08-05 14:48 ` Han-Wen Nienhuys
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=66e540fe05070802241cbf85ad@mail.gmail.com \
--to=mdjurfeldt@gmail.com \
--cc=djurfeldt@nada.kth.se \
--cc=guile-devel@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).