Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bbn!oberon!sargas.usc.edu!tli
From: tli@sargas.usc.edu (Tony Li)
Newsgroups: comp.os.vms
Subject: Re: Modifying Print Symbionts.
Message-ID: <4173@oberon.USC.EDU>
Date: Sat, 22-Aug-87 02:28:35 EDT
Article-I.D.: oberon.4173
Posted: Sat Aug 22 02:28:35 1987
Date-Received: Sun, 23-Aug-87 10:22:55 EDT
References: <8708211238.AA03687@ucbvax.Berkeley.EDU>
Sender: nobody@oberon.USC.EDU
Reply-To: tli@sargas.usc.edu (Tony Li)
Distribution: world
Organization: University of Southern California, Los Angeles, CA
Lines: 17

We have a working (but not completely bug-free) modified symbiont that
is written in C.

The best way of writing/debugging this type of problem is to set
yourself up so that you can use the debugger.  The modified symbiont
is run as part of a detached process.  By reassigning DBG$INPUT and
DBG$OUTPUT (in the system table), you can run the debugger on it and
yes, even see source.

By the way, before you ask, our print symbiont does something very
site-specific.

;-)
Tony Li - USC University Computing Services	"Fene mele kiki bobo"
Uucp: oberon!tli						-- Joe Isuzu
Bitnet: tli@uscvaxq, tli@ramoth
Internet: tli@sargas.usc.edu