From: Andy Wingo <wingo@pobox.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-devel@gnu.org
Subject: Re: after-gc-hook recently broken for bdwgc 7.2alpha CVS
Date: Tue, 12 Apr 2011 00:52:54 +0200 [thread overview]
Message-ID: <m3wrj0jt89.fsf@unquote.localdomain> (raw)
In-Reply-To: <87wrj49fqi.fsf@netris.org> (Mark H. Weaver's message of "Sat, 09 Apr 2011 01:05:25 -0400")
On Sat 09 Apr 2011 07:05, Mark H Weaver <mhw@netris.org> writes:
> Sometime between 2.0.0 and current stable-2.0, after-gc-hook has been
> broken on my system: "FAIL: gc.test: gc: after-gc-hook gets called".
>
> Both 2.0.0 and current stable-2.0 are built and linked with bdwgc
> 7.2alpha from CVS, circa 2011-03-27. This on gNewSense metad/mipsel
> (slightly modified Debian Lenny).
>
> Any ideas?
In 1.8, this hook was called after GC. In 2.0, it was only called on
explicit (gc), because the boehm GC doesn't have hooks like this. But
then in ec7f624d652eaf6e4cf06253101b4a986e1b9e8e I figured out an evil
way to get a hook: simply malloc an object, and resuscitate it in its
finalizer. The finalizer can then schedule the hook. If your hook is
not running though, that would indicate a problem.
So, no direct ideas, but good luck :-)
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-04-11 22:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-09 5:05 after-gc-hook recently broken for bdwgc 7.2alpha CVS Mark H Weaver
2011-04-11 22:52 ` Andy Wingo [this message]
2011-04-13 16:11 ` Ludovic Courtès
2011-04-17 21:46 ` Mark H Weaver
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=m3wrj0jt89.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.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).