Cause execution to continue from a given point and optionally set 1 or more 'go' breakpoints.
Syntax:
───┬─ G ──┬──┬─────────────────────┬──┬─────────────────┬──
├─ GS ──┤ └─ = ─── start-addr ──┘ └─── break-addr ─┬┘
└─ GT ──┘ │
└───── , ──────┘
Parameters:
Notes
No account is taken of the Kernel Debugger overhead when calculating the time interval.
When the Kernel Debugger re-enters, for whatever reason, the interval timer is cancelled until another GS command is executed.
If the reason for entry is for reasons other than the firing of a sticky or go breakpoint then in addition to cancelling the interval timer no time message displayed.
This is a convenience option that saves manually unhooking a Kernel Debugger trap vector handlers from the IDT. using a command sequence similar to:
VC n T VS n Gstart-addr
Warning: Be very careful to ensure that the start address is valid
for the privileged level and addressability of the code and data selectors
in use. If the Kernel Debugger attempts to load a segment register that
is invalid the system may trap in the debugger code.
If break-addr is omitted then the system continues execution until:
Results & Notes:
The system continues execution until the Kernel Debugger is re-entered. If the reason for entry is other than a breakpoint firing then the R command is automatically executed followed by one of the following command prompts:
>
If an error situation caused entry to the Kernel Debugger then a diagnostic message may be generated by the failing code writing directly to the Kernel Debugger's communications port.
If entry was caused by a Kernel Debugger trap handler receiving control then a message from the trap handler will be displayed. See the V command for details.
If a breakpoint caused the Kernel Debugger to receive control then commands associated with the breakpoint that fired will execute. See the B commands for details.
If a go-special was interrupted by a breakpoint firing then the following message appears before any output associated with the breakpoint:
Go Time (tics) = 017fb (hex) = 5145 (uSec)
This shows the time interval in both timer-ticks and equivalent number of micro-seconds.