From: hanwen@byrd.xs4all.nl (Han-Wen Nienhuys)
Subject: Re: scheme closures: crash during garbage collection
Date: Fri, 9 Jun 2006 21:54:58 +0000 (UTC) [thread overview]
Message-ID: <e6cqni$4ub$1@sea.gmane.org> (raw)
In-Reply-To: 87odx2ds0o.fsf@ossau.uklinux.net
In article <87odx2ds0o.fsf@ossau.uklinux.net>,
Neil Jerram <neil@ossau.uklinux.net> wrote:
>> guile-gnome (up to v. 2.7.98, most recent as of this writing) can
>> call scm_gc_unprotect_object() during a scheme garbage collector
>> sweep, which is a fatal error in guile-1.8. In earlier versions
>> of guile, it is not a fatal error (but still, I think you're not
>> supposed to do it.)
>
>Many thanks for this great analysis.
>
>It seems to me, though, that the same kind of situation, leading to
>wanting to call scm_gc_unprotect_object during GC, is likely to arise
>in any sufficiently complex application, and hence that we should
>support this within Guile itself.
>
>(I'm not personally familiar with the GC code, but it may be that the
>new restriction in 1.8 against doing this was not strongly intended,
>but more of a shortcut that was then forgotten.)
>
>Can people more familiar with the GC code comment on whether this fix
>is feasible?
No, MV thinks it's a bad idea, and I agree with him.
See
http://thread.gmane.org/gmane.lisp.guile.devel/4117/focus=4160
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-06-09 21:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <64e2f6fe0606081528m4e5f9979yff9b8294ecedf6d2@mail.gmail.com>
2006-06-09 19:54 ` scheme closures: crash during garbage collection Neil Jerram
2006-06-09 21:54 ` Han-Wen Nienhuys [this message]
2006-06-10 9:40 ` Marius Vollmer
2006-06-12 22:34 ` Neil Jerram
2006-06-12 23:33 ` Han-Wen Nienhuys
2006-06-12 23:45 ` Neil Jerram
2006-07-08 15:06 ` Marius Vollmer
2006-07-12 21:48 ` Neil Jerram
2006-10-27 9:49 ` Andy Wingo
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='e6cqni$4ub$1@sea.gmane.org' \
--to=hanwen@byrd.xs4all.nl \
--cc=hanwen@lilypond.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).