Hello,

I might be able to figure this out on my own, but perhaps one of you has
the answer and can save me some detective work...

I'm using CMUCL 18d on Linux/Intel.

I want to fire up a lisp, load some things, make some modifications, and
then save the Lisp core image so that later I can start right where I left
off.

The problem: When running a Lisp stand-alone, the SAVE-LISP function and
-core switch on startup seem to work fine.  However, I like to run under
Hemlock, in a slave Lisp.  When I try to call SAVE-LISP in the slave, it
says that it is doing a purify, but then the system goes catatonic and a
short time later the slave dies.  The core-file that I asked for seems to
have been created, but the core file cannot be run in a new Lisp -- it just
freezes up.

Presumably there's something about the way the I/O streams are set up in
the slave Lisp that confuses SAVE-LISP.

Do any of you have this working?  Is there some simple trick I'm missing?

If it's impossible to do a save-restore under Hemlock, maybe I should bite
the bullet and switch over to ilisp.  Does this work better there?

Thanks,
Scott

===========================================================================
Scott E. Fahlman                        Internet:  [EMAIL PROTECTED]
Principal Research Scientist            Phone:     412 268-2575
Department of Computer Science          Fax:       412 268-5576
Carnegie Mellon University              Home:      www.cs.cmu.edu/~sef
5000 Forbes Avenue                      Mood:      :-)
Pittsburgh, PA 15213                    
===========================================================================

Reply via email to