From:	SMTP%"carl@SOL1.GPS.CALTECH.EDU" 25-APR-1994 12:34:50.59
To:	EVERHART
CC:	
Subj:	Re: SUM: SYS$WAKE() doesn't wake...

From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
X-Newsgroups: comp.os.vms
Subject: Re: SUM: SYS$WAKE() doesn't wake...
Date: 25 Apr 1994 15:38:12 GMT
Organization: HST Wide Field/Planetary Camera
Lines: 33
Distribution: world
Message-ID: <2pgo54$9m7@gap.cco.caltech.edu>
Reply-To: carl@SOL1.GPS.CALTECH.EDU
NNTP-Posting-Host: sol1.gps.caltech.edu
To: Info-VAX@CRVAX.SRI.COM
X-Gateway-Source-Info: USENET

In article <2pgfnf$rat@usenet.pa.dec.com>, diewald@virrus.zko.dec.com (Jeff Diewald) writes:
=A better answer was given by Arne Vajhoej, in his reply.  (Thanks, Arne!) If 
=you:
=
=  $ DEFINE DBG$PROCESS NONE
=
=this changes the debugger configuration from a two process debugger to a 
=one process debugger.  Instead of activating just the kernel with the image
=to be debugged, both the kernel and main are activated.  These images share
=the address space with your program.
=
=Since the kernel and the main are in the same process, there's no need to use
=$HIBER and $WAKE to synchronize things - so the debugger doesn't.  You should
=be able to cleanly and simply debug your program.
=
=The DBG$PROCESS NONE feature has some drawbacks.  First, you can't use the
=Motif GUI in this mode.  Second, DBG$PROCESS NONE is not supported, so some 
=other commands and options may not be available in this mode.  Third, since 
=both the main and kernel images are in your process space, that process is 
=going to require a lot more memory.  

And, if you're absent-minded enough you can't remember
	$ DEFINE DBG$PROCESS NONE
you can always
	$ SET PROCESS/PRIV=NOTMPMBX
--------------------------------------------------------------------------------
Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL

Disclaimer:  Hey, I understand VAXen and VMS.  That's what I get paid for.  My
understanding of astronomy is purely at the amateur level (or below).  So
unless what I'm saying is directly related to VAX/VMS, don't hold me or my
organization responsible for it.  If it IS related to VAX/VMS, you can try to
hold me responsible for it, but my organization had nothing to do with it.