On 10/31/06, Edi Weitz <[EMAIL PROTECTED]> wrote:
On x86 you could try this:
http://www.cons.org/cmucl/doc/lispserver.html
Edi,
Many thanks for mentioning this (we do run on x86); I'll get a chance
to explore that option in the next few days
In the end (or at least for right now), I wound up going back to using
detachtty/attachtty -- I find it is a good solution, provided all the
jobs can be started under detachtty in the first place (the particular
processes I wanted to monitor were kicked off by a complex set of cron
and startup scripts, and my first reaction was not to touch any of
that stuff).
If lispserver is not the solution, though, I'd be curious to know what
it would take to have a future version of CMUCL be able to do this; I
know there's a gdb-like debugger (ldb) embedded inside CMUCL, so how
much work would it take to allow it to communicate and attach to other
CMUCL processes?
