I have had experience doing this. You have a couple of options either
of which are easy to implement. 1) When wanting to debug the listener
process put in a infinite loop where you want to start debugging and
then start the client process. Attach XDB to the process ID and reset
the process pointer to the next statement beyond the infinite loop. 2)
There is an option which tells the debugger when activated to send
output and read input from the system console. There is an example in
the manual about this. I believe the symbolic debugger manual. It has
been about 4 years since I have needed to do this.
Hope this helps.

James

On Tue, 13 May 1997 14:40:34 +0200, Chris Breemer
<[log in to unmask]> wrote:

>Hi listers,
>
>I wonder if anybody has experience with debugging a server-only program on the
> 3k.
>I don't mean writing a logfile, but really invoking the symbolic debugger on
the
>server program.
>
>The wild idea is that when the socket listener normally starts the server
> program,
>it would now start XDB.PUB.SYS with the server program as argument. It would
use
>the STARTSESS command to put that dialog on the console screen. Now since this
>is another session I'm not sure that open sockets etc. would be inherited.
>
>Before diving in the mud, I just want to ask if anybody has ever tried stuff
> like
>this ? Or has any other good suggestions for realtime debugging of a server
> program ?
>
>TIA
>        chris