Re: Bug: Unbound variable:

[Ludovic Courtès]

Hi,

"Linas Vepstas" <address@hidden> writes:

> In guile-1.8.5 (haven't yet tried 1.8.6) I'm seeing a strange bug:
> a program that has been running a while (12-24 hours) and
> approaching an out-of-memory condition (system on verge
> of swapping to disk) will suddenly get an 'Unbound variable'
> error on a variable that is heavily in use (dozens or maybe
> thousands of calls per second).  This system has only *one*
> thread in guile mode.

Are you able to get a meaningful backtrace when that exception is
raised?  Can you reproduce that with a simple example?  Is your program
doing something nasty with threads?  :-)

Thanks,
Ludo'.