Function Stepping (Windows Embedded CE 6.0)
1/5/2010
When debugging, you can step into, step over, or step out of a function.
- The Step Into command causes the debugger to execute the next statement and then pause. If the next statement is a function, the Step Into command causes the debugger to enter the function and pause at the beginning of it.
- The Step Over command causes the debugger to execute the function and to pause after the function is completed.
- The Step Out command causes the debugger to finish executing the current function and to pause when the function is exited.
Stepping works for the current process or thread only. To step through a section of code, you must first insert a breakpoint. When that breakpoint is reached, you can begin stepping through the code.
Note
On an ARM CPU, the compiler generates a __finally block as if the _finally block were a separate function. While execution is inside a __finally block, the debugger shows two frames of the current function. When debugging source code, use the Step Into command to step from a __leave statement into a __finally block.
See Also
Tasks
Stepping Over a Function
Stepping Out of a Function
Stepping Into a Function