Debug tool window
Regardless of the selected tab, you can always use the following toolbar controls in the left part of the window:
Tooltip and Shortcut
Click this button to stop the current application and run it again.
When an application is paused, click this button to resume program execution.
Click this button to pause program execution.
Click this button to terminate the current process externally by means of the standard
Click this button to open the Breakpoints dialog where you can configure breakpoints behavior.
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:
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.
Tooltip and Shortcut
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.
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.
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.
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.
Click this button to . evaluate expressions.