This is the mail archive of the
guile@sourceware.cygnus.com
mailing list for the Guile project.
Re: guile-gtk 0.17
- To: Marius Vollmer <mvo AT zagadka.ping.de>
- Subject: Re: guile-gtk 0.17
- From: Greg Badros <gjb AT cs.washington dot edu>
- Date: 17 Sep 1999 11:24:24 -0700
- Cc: guile AT sourceware.cygnus dot com, Ariel Rios <jarios AT usa dot net>, Miroslav Silovic <silovic AT zesoi.fer.hr>, Martin Baulig <martin AT home-of-linux dot org>
- References: <19990915221659.26979.qmail@.netaddress.usa.net> <qrrr9jzu8bg.fsf@elwha.cs.washington.edu> <87iu5afy4c.fsf@zagadka.ping.de>
Marius Vollmer <mvo@zagadka.ping.de> writes:
> Greg Badros <gjb@cs.washington.edu> writes:
>
> > The bugs I've seen in the GC are my main short-term problem.
>
> Bugs that surface during GC are indeed very hard to track down. My
> best advice is to try to narrow down the cause of it to the simplest
> piece of code possible. This might be difficult, too, because GC
> invocation is quite asynchronous. You might even want to patch
> libguile to run the GC more deterministically, like after each cons.
This would be a nice run-time option in developer builds of guile:
(set-gc-after-each-cons! #t)
It'd be expensive (even noticeable, perhaps, when turned off), but could
really help on these tricky problems.
We have this in system.scwmrc to help with debugging startup problems:
;; (set-load-processing-frequency! 1)
;; (add-hook! load-processing-hook (lambda (n) (display n) (newline) (gc)))
Greg