It has been tested under the distributed XM monitor, I think it
will work generally, but if you have any problems, let me know
and I'll check it out.
In order to debug a privileged foreground or system job (a non-virtual
program not running under VBGEXE), do the following:
.LOAD SD
.{F|S}RUN program_name[/pause]
.RUN DEBUG
DEBUG>job_name (same as program_name unless it was run /NAME:name)
DEBUG>^C
Note: alternatively, you could place DEBUG.SAV on your system
volume and issue the command:
.DEBUG job_name
At this point, breakpoints executed by the job should be directed
to SD (or whatever debugger you are using)
I include a portion of the abstract page of the source for explanation:
; DEBUG
;
; The purpose of this program is to provide a tool for debugging
; foreground or system jobs under RT11 using DBG-11. The reason
; this program is needed is that the breakpoint trap vector is
; a context-switched location, and unless it has been specified
; for a foreground or system job, it causes a trap to location
; 0 which executes the BIC R0,R0 and .ASTX, causing the job to
; abort.
;
; This program duplicates the contents of the current physical
; breakpoint trap vector in the appropriate locations in the
; impure area of the specified job.
