pc (Step to Next Call)
The pc command executes the program until a call instruction is reached.
[~Thread] pc [r] [= StartAddress] [Count]
pc [r] [= StartAddress] [Count]
Specifies threads to continue executing. All other threads are frozen. For more information about the syntax, see Thread Syntax. You can specify threads only in user mode.
Turns on and off the display of registers and flags. By default, the registers and flags are displayed. You can disable register display by using the pcr, pr, tr, or .prompt_allow -reg commands. All of these commands control the same setting and you can use any of them to override any previous use of these commands.
You can also disable register display by using the l-os command. This setting is separate from the other three commands. To control which registers and flags are displayed, use the rm (Register Mask) command.
Specifies the address where the debugger begins execution. Otherwise, the debugger begins at the instruction that the instruction pointer points to. For more information about the syntax, see Address and Address Range Syntax.
Specifies the number of call instructions that the debugger must encounter for this command to stop. The default value is one.
User mode, kernel mode
Live debugging only
For more information about related commands, see Controlling the Target.
The pc command causes the target to begin executing. This execution continues until a call instruction is reached or a breakpoint is encountered.
If the program counter is already on a call instruction, the entire call is executed. After this call is returned, execution continues until another call is reached. This execution, rather than tracing, of the call is the only difference between pc and tc (Trace to Next Call).
In source mode, you can associate one source line with multiple assembly instructions. The pc command does not stop at a call instruction that is associated with the current source line.