Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!CHAMARTIN.AI.MIT.EDU!jinx
From: jinx@CHAMARTIN.AI.MIT.EDU (Guillermo J. Rozas)
Newsgroups: comp.lang.scheme.c
Subject: scheme_suspend
Message-ID: <8903222047.AA10533@chamartin.AI.MIT.EDU>
Date: 22 Mar 89 20:47:08 GMT
References: <PK.89Mar22193509@voltti.tut.fi>
Sender: daemon@bloom-beacon.MIT.EDU
Reply-To: jinx@zurich.ai.mit.edu
Distribution: inet
Organization: The Internet
Lines: 22


       Under what circumstances does it write it?
       If it's an image dump, you should be able to specify it after the
       -band option when starting scheme.

    I get it once in a while, but I haven't been able to pinpoint the cause.
    It seems that it has something to do with GNU Emacs killing the scheme process.

Scheme dumps a scheme_suspend band when it receives the Unix SIGHUP signal.
This is done so that when a connection is dropped, any work done in
the Scheme environment is not lost.

    I tried to say 
		      % scheme -band scheme_suspend
    but didn't get much out of it. Scheme was just silent for a while, and when I
    finally got a prompt from it, it didn't know about any of the functions I had defined.

As always, you can examine the environment by using the WHERE procedure.

(where)

enters the environment inspector.