Stepping through

On the top panel of the Debug window, you will find the stepping buttons:

• Step Over ( or F8) skips the current line (even if it includes function calls) and pauses in the beginning of the next line.

  If the skipped functions contain breakpoints, the debugger will stop at them. To skip any breakpoints on the way, use Force Step Over ( or Alt+Shift+F8).

• Step Into ( or F7) steps into the function to show what is happening inside. Use this option when you are not sure the function is returning a correct result.

  If you don't want to step into standard library code (std, core, alloc), go to Settings | Build, Execution, Deployment | Debugger | Stepping and set the Do not step into stdlib checkbox.

  

• Force Step Into (Alt+Shift+F7 or via the three dot menu) steps into any functions (even those skipped by Step Into).

  Force Step Into is helpful if you want to explore a function whose source code is unavailable. In such cases, this action steps into disassembled code.

• Step Out (Shift+F8 or via the three dot menu) leaves the current function taking you back to the caller function.

• Run to cursor (Alt+F9 or via the three dot menu) continues executing code until the position of the caret is reached.

  Also, you can Run to Cursor by clicking the line number in the gutter.

  To skip any breakpoints on the way, use Force Run to Cursor (Run | Debugging Actions | Force Run to Cursor, Control+Alt+F9, or via the three dot menu).