Debug tool window
When you start a debugger session, the Debug tool window appears. Use this window to control the debugger session, display and analyze the program data (frames, threads, variables, and so on), and perform various debugger actions.
The available debug sessions are separated into tabs in the top part of the Debug tool window.
All the information like inline variable values and execution point is shown for the selected session tab. This is important if you are running several debug sessions in parallel that use the same code.
The Debug tool window shows the following tabs for each session:
Frames: lets you navigate in call stacks of the threads.
Variables: lists the variables available in the current context and lets you analyze and modify the program state.
Watches: lets you manage watches. By default, watches are shown on the Variables tab for more efficient use of the screen space. If you have a lot of watches, consider viewing them in a separate tab.
Console: displays the program output.
For local sessions, the tab works the same as when you just run the program without the debugger attached.
LLDB: provides a console for LLDB command-line debugging.
Memory View: shows raw memory of the running process.
Click and select which tabs you want to see.
Restore default layout
If you changed the layout of the Debug tool window and don't like the new arrangement, you can revert it to the default state.
Click in the top-right corner of the Debug tool window, then click Restore Default Layout.
You can arrange the tabs to fit your preference. You can move a tab to another location or group a tab with another tab, so that they share the same space on the screen.
Drag the tab header to the desired location. The semi-transparent frame indicates the destination.
Regardless of the selected tab, you can always use the following toolbar controls:
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.
When the button is pressed in the toolbar of the Debug tool window, all the breakpoints in the project are muted, and their icons become grey: .
You can temporarily mute all breakpoints in the project to execute the program without stopping at breakpoints.
The most commonly used actions are located directly on the toolbar. The rest of the actions are available via the button:
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.
Force Step Over
Click this button to have the debugger step over the method even if this method has breakpoints inside.
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 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.
Force Run to Cursor
If there are breakpoints between the current execution point and the target statement, you can force the debugger to skip these breakpoints with the Force Run to Cursor command Ctrl+Alt+F9.
Click this button to evaluate expressions.