unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Han-Wen Nienhuys <hanwenn@gmail.com>, Guile Devel <guile-devel@gnu.org>
Cc: lilypond-devel <lilypond-devel@gnu.org>
Subject: Re: Java finalization & smobs?
Date: Fri, 10 Dec 2021 18:10:29 +0000	[thread overview]
Message-ID: <108163487740b9b0a35bc41895df1524b1058e70.camel@telenet.be> (raw)
In-Reply-To: <CAOw_e7afsHz82kyje1tT+=wDk6BnQDO_e6J-E9w-25aa0ozPJA@mail.gmail.com>

Han-Wen Nienhuys schreef op vr 10-12-2021 om 15:59 [+0100]:
> On the one hand, the docs for smobs state "must assume .. all SCM
> values that it references have already been freed and are thus
> invalid", which suggests that smob freeing happens in random order,
> which is consistent with what we see. On the other hand, Guile sets
> up
> BDWGC with GC_java_finalization=1, which should keep GC dependencies
> of an object alive until the object itself is finalized, and I think
> we have observed the mark calls that make this happen.
> 
> which of the two is it?

I assume that the fact that Java-style finalization is used, is
considered an internal implementation detail.

That doesn't explain why things are going wrong, of course.

Greetings,
Maxime




      parent reply	other threads:[~2021-12-10 18:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-10 14:59 Java finalization & smobs? Han-Wen Nienhuys
2021-12-10 18:00 ` Maxime Devos
2021-12-10 18:02 ` Maxime Devos
2021-12-10 18:10 ` Maxime Devos [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=108163487740b9b0a35bc41895df1524b1058e70.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=guile-devel@gnu.org \
    --cc=hanwenn@gmail.com \
    --cc=lilypond-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).