We've had a /200 running with Jonathan's update kit (to fix cerror.s and
dl_open) for a week or so.  Last Friday, the system "halted" with a
"db>" prompt.  I was able to continue using the "c" command.  Next time
it happens, what information can I gather to try and trace the problem?

--

Philip J. Tait.....AlliedSignal Engines, Phoenix, Az.....pjt@phxase.allied.com