Debug tool window

Rerun

Click this button to stop the current application and run it again.

Resume Program

When an application is paused, click this button to resume program execution.

Pause Program

Ctrl+Pause

Click this button to pause program execution.

Stop

Click this button to terminate the current process externally by means of the standard shutdown script.

View Breakpoints

Click this button to open the Breakpoints dialog where you can configure breakpoints behavior.

Mute Breakpoints

Use this button to toggle breakpoints status.

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

Debugger Settings

Opens the menu with the following options:

• Open Files in Preview Tab: select this option to open files in a preview tab when the corresponding frame is selected.

• Show Variable Values in Editor: 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 Variables 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 option is enabled, the message shown is Collecting data, and after that the debugger shows the variables' values.

  • Asynchronously: If this option is enabled, 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 option is enabled, 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.

Pin Tab

Click this button to pin or unpin the current tab. You may need to pin a tab to prevent it from closing automatically when the maximum number of tabs is reached in this window.

Rerun

Click this button to stop the current application and run it again.

Resume Program

When an application is paused, click this button to resume program execution.

Pause Program

Ctrl+Pause

Click this button to pause program execution.

Stop

Click this button to terminate the current process externally by means of the standard shutdown script .

View Breakpoints

Click this button to open the Breakpoints dialog where you can configure breakpoints behavior.

Mute Breakpoints

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.

Settings

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 option is enabled, the message shown is Collecting data, and after that the debugger shows the variables' values.

  • Asynchronously: If this option is enabled, 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 option is enabled, 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.

Pin Tab

Click this button to pin or unpin the current tab. You may need to pin a tab to prevent it from closing automatically when the maximum number of tabs is reached in this window.

Show Execution Point

Click this button to highlight the current execution point in the editor and show the corresponding stack frame in the Frames pane.

Step Over

Click this button to execute the program until the next line in the current method or file, skipping the methods referenced at the current execution point (if any). If the current line is the last one in the method, execution steps to the line executed right after this method.

Step Into

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

Force Step Into

Click this button to have the debugger step into the method called in the current execution point even if this method is to be skipped.

Step Out

Click this button to have the debugger step out of the current method, to the line executed right after it.

Run to Cursor

Click this button to resume program execution and pause until the execution point reaches the line at the current caret 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.

tip

Use this action when you need a kind of a temporary breakpoint at a specific line, where program execution should not be interrupted.

Evaluate Expression

Click this button to evaluate expressions.

Show Execution Point

Click this button to highlight the current execution point in the editor and show the corresponding stack frame in the Frames pane.

Step Over

Click this button to execute the program until the next line in the current method or file, skipping the methods referenced at the current execution point (if any). If the current line is the last one in the method, execution steps to the line executed right after this method.

Step Into

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

Force Step Into

Click this button to have the debugger step into the method called in the current execution point even if this method is to be skipped.

Step Out

Click this button to have the debugger step out of the current method, to the line executed right after it.

Run to Cursor

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.

tip

Use this action when you need a kind of a temporary breakpoint at a specific line, where program execution should not be interrupted.

Evaluate Expression

Click this button to evaluate expressions.