Xref: utzoo comp.lang.scheme:863 comp.lang.lisp.x:12
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!rpi!leah!bingvaxu!sunybcs!sbcs!nyit!zilla
From: zilla@nyit.UUCP (John Lewis)
Newsgroups: comp.lang.scheme,comp.lang.lisp.x
Subject: xscheme bug
Keywords: xscheme scheme
Message-ID: <362@nyit.UUCP>
Date: 16 Oct 89 03:10:31 GMT
Followup-To: comp.lang.scheme
Organization: NYIT Computer Graphics Laboratory, Old Westbury, NY
Lines: 10


there is a bug in xscheme0.17's (restore) function.  the bug is that garbage
collection should be inhibited during the main part of xlirestore().  This
is because the image is restored in node-array order, rather than obarray order.
For example, strings may be restored before the symbols which refer to them,
and a gc before the corresponding symbol is restored will remove the string (set
its type to FREE).  routines called in xlirestore (e.g. getvspace()) can
trigger gc.
  A fix is simply to set a flag inhibiting gc during the main part of 
xlirestore.  dbetz confirmed that this is a reasonable fix.