From:	SMTP%"diewald@virrus.zko.dec.com"  1-SEP-1994 11:41:24.98
To:	EVERHART
CC:	
Subj:	Re: How to debug a print symbiont under axp v6.1?

From: diewald@virrus.zko.dec.com (Jeff Diewald)
X-Newsgroups: comp.os.vms
Subject: Re: How to debug a print symbiont under axp v6.1?
Date: 1 Sep 1994 13:51:10 GMT
Organization: Digital Equipment Corporation
Lines: 47
Distribution: world
Message-ID: <344m8e$d59@usenet.pa.dec.com>
Reply-To: diewald@virrus.zko.dec.com (Jeff Diewald)
NNTP-Posting-Host: virrus.zko.dec.com
X-Newsreader: mxrn 6.18-9
To: Info-VAX@CRVAX.SRI.COM
X-Gateway-Source-Info: USENET


In article <940826111122.20200570@PFC.MIT.EDU>, Mark London <MRL@PFC.MIT.EDU> writes:
|>Hi
|>	I'm trying to debug a print symbiont on my Alpha running v6.1.  On the
|>vax, what I used to do was to link the program with /DEBUG and then assign
|>DBG$INPUT and DBG$OUTPUT in the group table lnm$group_000001 to a terminal. 
|>On the Alpha, this does not work.  The error message from the queue manager
|>is:

Mark,

   You might take a look at the chapter on "Debugging Special Cases" in the 
latest OpenVMS Debugger manual.  There is a section on debugging screen 
oriented programs that might be able to give you some ideas.

   Another option to consider is the improved CONNECT command.  You can
connect to another process, including another process not in your job
tree.  (It must have the same UIC.)  To do this, make sure that the same
DEBUG logicals are defined for the print symbiont process and your 
working terminal. (most important is DBG$PROCESS set to MULTIPROCESS)
When you have done this, fire up the kept debugger (DEBUG/KEEP) - the 
debugger without a program - from your working terminal.  Inside this
debugger, issue the CONNECT command with the process ID of the symbiont.
While I haven't tried this on a symbiont, I have done it with other
spawned processes not in my job tree.

   You can also DISCONNECT from a running process and let it keep running
as if the Debugger hadn't been there.  This allows you to connect (or reconnect)
to a long-running process as needed in order to troubleshoot.  

   See the chapter on "Debugging Multiprocess Programs" in the latest OpenVMS 
Debugger manual for more details on CONNECT/DISCONNECT.  I'd urge you to read
this carefully before you start trying to do an interesting connection such
as yours, due to some of the restrictions on this support.  (e.g. the process
you connect to must have a CLI, the debugger logicals have to match in both
processes, etc.)

   You can also find information on-line in the HELP system.  Check out
CONNECT, DISCONNECT, and New_Features_AXP for more details.
-----------------------------------------------------------------------------
	Jeff Diewald			EASYNET:   VIRRUS::DIEWALD
	DECladebug group		INTERNET:  diewald@virrus.zko.dec.com
	Digital Equipment Corp.

Note: I don't read every article in this group.  If you have debugger 
questions, I may be able to get you an answer.  You're much more likely to 
get an answer if you put "Debug" somewhere in your subject line.

