* after-gc-hook recently broken for bdwgc 7.2alpha CVS
@ 2011-04-09 5:05 Mark H Weaver
2011-04-11 22:52 ` Andy Wingo
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: Mark H Weaver @ 2011-04-09 5:05 UTC (permalink / raw)
To: guile-devel
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?
Best,
Mark
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: after-gc-hook recently broken for bdwgc 7.2alpha CVS
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
2011-04-13 16:11 ` Ludovic Courtès
2011-04-17 21:46 ` Mark H Weaver
2 siblings, 0 replies; 4+ messages in thread
From: Andy Wingo @ 2011-04-11 22:52 UTC (permalink / raw)
To: Mark H Weaver; +Cc: guile-devel
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/
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: after-gc-hook recently broken for bdwgc 7.2alpha CVS
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
@ 2011-04-13 16:11 ` Ludovic Courtès
2011-04-17 21:46 ` Mark H Weaver
2 siblings, 0 replies; 4+ messages in thread
From: Ludovic Courtès @ 2011-04-13 16:11 UTC (permalink / raw)
To: guile-devel
Hi Mark,
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".
FWIW Hydra has had this problem in the GCC 3.x build job:
http://hydra.nixos.org/build/1043456
It first had the problem when this change set was introduced:
http://git.savannah.gnu.org/cgit/guile.git/diff/?id=7f22442b2af85ea9db89c84fbd3acb6a96ee13fd&id2=ad301b6d58c2ca054ebe1fdfaf7357e61311a977
Thanks,
Ludo’.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: after-gc-hook recently broken for bdwgc 7.2alpha CVS
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
2011-04-13 16:11 ` Ludovic Courtès
@ 2011-04-17 21:46 ` Mark H Weaver
2 siblings, 0 replies; 4+ messages in thread
From: Mark H Weaver @ 2011-04-17 21:46 UTC (permalink / raw)
To: guile-devel
The "after-gc-hook" test now passes on my system. Thanks Andy! :)
Mark
I wrote:
> 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).
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2011-04-17 21:46 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2011-04-13 16:11 ` Ludovic Courtès
2011-04-17 21:46 ` Mark H Weaver
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).