Setting the Next Statement to Execute
Other versions of this page are also available for the following:
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/27/2008
You can choose the next statement to execute while the debugger is a break state, both in the Source window and in the Disassembly window.
To set the next statement to execute in a source window while the debugger is in the break state
In a source window, move the insertion point to the statement or instruction that you want to execute next.
Right-click, and then choose Set Next Statement.
To set the next disassembly instruction to execute while the debugger is in a break state
In the Disassembly window, move the insertion point to the disassembly instruction you want to execute next.
Right-click, and then choose Set Next Statement.
You can use the Set Next Statement command to skip a section of code and continue to debug other sections; for example, a section that contains a known bug.
Because the intervening code is not executed, use this command with caution.
You can also return to an earlier statement to retest your application, using different values for variables.