Re: Lispm FORTRAN goes to Hyperspace

[barmar@Think.COM (Barry Margolin)]

    Date: Fri, 2 Aug 1991 14:02 EDT
    From: moon@cambridge.apple.com (David A. Moon)

    Try using the FEP debugger on an Ivory based machine to look around,
    see whether your hung Lisp Listener is the running process or is
    blocked, etc.  Get to the FEP and use the Debug command.  The Ivory
    FEP debugger is quite knowledgeable about the various system data
    structures.

The FEP debugger on L machines is also usable for this, although it's
not as nice as the IFEP debugger.  It's certainly good enough if you
just want to know where the system is spending its time when it's
unresponsive.  Don't forget to use c-m-S to switch to the regular stack
when you start it; hyper-control-Function's interrupt is serviced on the
auxiliary stack.

    Another wormhole you might be able to use is to press the Function
    and Suspend keys, which puts you into a break loop in the cold load
    stream, with process scheduling disabled.  You can't use commands or
    the mouse, but between the DESCRIBE function and the ZL:DBG function,
    which takes a process as its argument and puts you into the Lisp
    debugger looking at that process, you can find out a lot.  Another
    trick is (accept-from-string 'sys:process "<name of process>") to
    get something that you'd normally get by pointing the mouse at it.

Instead of (zl:dbg (accept-from-string ...)) you can use the CP command
"Debug Process <name of process>".  The cold load stream runs the
command processor just like any other break loop.

                                                barmar