Step Commands: Overview
Each step command operates either at the source statement
level, or at the machine (or assembly code) level. Once you know
what step command you want to use, select the appropriate one
from the Actions menu or by using the appropriate toolbar button
on the debugger toolbar.
Here is a brief summary of available step commands:
- step into
- Executes the current statement. If the current statement
contains a function call, execution stops at the first
statement or instruction of the first called function in
the statement. Otherwise, execution stops at the
statement that logically follows the current statement
within the same function.
- step over
- Executes the current statement. Execution stops at the
statement that logically follows the current statement
within the same function, or in the calling function if
the statement you step over is a return statement.
Function calls within the statement are stepped over and
execution does not stop within them, unless the debugger
encounters a breakpoint within a called function.
- step debug
- Executes from the current statement up to the next
statement for which debugging information is available.
This statement may be in the current function, or in any
function called while the statement is executed. For
example, if the statement stepped over is a call to
func1, where func1 calls func2 and func2 calls func3, and
debug information is only available for func3, execution
would stop in the first statement of func3. Use step
debug instead of step into when you want to step into
only those functions that have source code views
available.
- machine step into
- Executes the current machine language instruction. If the
current instruction is a call, execution stops at the
first instruction within the called function or routine.
Otherwise, execution stops at the instruction that
logically follows the current instruction.
- machine step over
- Executes the current machine language instruction.
Execution stops at the instruction that logically follows
the current instruction. Calls within the statement are
stepped over and execution does not stop within them,
unless the debugger encounters a breakpoint within the
called code.
- return step
- Executes from the current statement or instruction,
through the return from the current function. Execution
stops at the statement or instruction following the call
to the function that you just returned from. If the view
on return is a source view, execution may stop at the
same statement that issued the original call, if that
statement contains multiple function calls. You can use a
combination of Step into and Step return commands to step
into each function in a statement containing multiple
function calls.
Note that, for all step commands except Machine step into,
execution stops before the command completes if an enabled
breakpoint is encountered.
If a function terminates on a signal or exception when
stepping through function calls, you may not always stop at the
expected point.

Step over a Function
Step through Machine Language
(Disassembly) Instructions

Machine Step Into
Machine Step Over