Debug tool window

Click this button to pause program execution.

Use this button to toggle breakpoints status.

You can temporarily mute all the breakpoints in a project to execute the program without stopping at breakpoints.

Click this button to open the menu with the following options:

• Show Values Inline: select this option to enable the Inline Debugging feature that allows viewing the values of variables right next to their usage in the editor.

• Sort Values Alphabetically: select this option to sort the values in the Variables pane in the alphabetical order.

• Unmute Breakpoints on Session Finish: select this option to re-enable all disabled breakpoints after the debugging session has been finished.

• Show Return Values: select this option to display the return values of the executed functions in the current frame while stepping.

• Simplified Variables View: Select this option to include the following names into the Special Variables group:

  • all variables with the dunder names.

  • all instances of function, classobj and module.

  • all the IPython internal variables, if debug console with IPython has been started.

• Variables Loading Policy. You can choose one of the following policies:

  • Synchronously: If this check command is selected, the message shown is Collecting data, and after that the debugger shows the variables' values.

  • Asynchronously: If this check command is selected, the variables in the debugger are loaded separately (asynchronously). In this case, if loading a variable takes a long time, the debugger shows ...Loading Value message, and only after that it shows its value or the Loading timed out message, if the variable is too slow. Mind the warning message that suggest switching to the on demand mode.

  • On demand: If this check command is selected, the debugger shows Show Value message. Click it to enable loading.

  Note that any changes in the loading policies become effective after you rerun the debugging process.

Click this button to have the debugger step into the method called at the current execution point.

Click this button to resume program execution and pause until the execution point reaches the line at the current cursor location in the editor. No breakpoint is required. Actually, there is a temporary breakpoint set for the current line at the caret, which is removed once program execution is paused. Thus, if the caret is positioned at the line which has already been executed, the program will be just resumed for further execution, because there is no way to roll back to previous breakpoints. This action is especially useful when you have stepped deep into the methods sequence and need to step out of several methods at once.

If there are breakpoints set for the lines that should be executed before bringing you to the specified line, the debugger will pause at the first encountered breakpoint.