DEBUG CTRL-C — VMS C_3.0
When entered from within a debugging session, aborts the
execution of a debugger command or interrupts program execution
without interrupting the debugging session. This is useful when,
for example, the program is executing an infinite loop that does
not have a breakpoint, or you want to abort a debugger command
that takes a long time to complete. The debugger prompt is then
displayed, so that you can enter debugger commands.
Format:
<CTRL/C>
After a CTRL/C interruption, any processes of a multiprocess
program that were executing images are in the "interrupted"
state.
If your program already has a CTRL/C AST service routine enabled,
use the SET ABORT_KEY command to assign the debugger's abort
function to another CTRL-key sequence. Note, however, that many
CTRL- key sequences have VMS predefined functions, and the SET
ABORT_KEY command enables you to override such definitions (see
the VMS DCL Concepts Manual). Some of the CTRL-key characters
not used by the VMS operating system are G, K, N, and P.
If your program does not have a CTRL/C AST service routine
enabled, and you assign the debugger's abort function to another
CTRL-key sequence, the CTRL/C sequence then behaves like CTRL/Y
--- that is, it interrupts the debugging session and returns you
to DCL level.
Do not use CTRL/Y from within a debugging session. Always use
either CTRL/C or an equivalent CTRL-key sequence established with
the SET ABORT_KEY command.
Note that you can use the SPAWN and ATTACH commands to leave and
return to a debugging session without losing the debugging
context.
Additional information available:
Example
DBG> GO
...
<CTRL/C>
%DEBUG-W-ABORTED, command aborted by user request
DBG> EXAMINE/BYTE 1000:101000 !should have typed 1000:1010
1000: 0
1004: 0
1008: 0
1012: 0
1016: 0
<CTRL/C>
%DEBUG-W-ABORTED, command aborted by user request
DBG>
This example shows how to use the CTRL/C sequence to,
first, interrupt program execution, and then, abort
the execution of a debugger command.