You can use the Debug Step Into command to step over any function that does not have source code information available. For example, you may not be sure whether a call points to a function in your source code, or to a runtime library function for which no source is available. Usually, you only want to debug your own source code statements, not runtime library or operating system functions.
When you use Debug Step Into, the debugger steps over the current statement or instruction and stops at the next source code statement. If the current statement or instruction is a call and there is no source code available within the called function (or a function it in turn calls), the next source code statement is the statement that logically follows the return from the call.
![]()
Step Into a Function
Step Through Source
Code
![]()
Summary of
Step Commands
Source-Level
Step Commands
