Debug tool window

Sessions

The available debug sessions are separated into tabs in the top part of the Debug tool window.

If you enable Services window for specific run/debug configurations, the entire view of the Debug window will be displayed inside the Services window when you debug any of these configurations.

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 classes.

Tabs

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. The only difference is that debugger output (for example, log messages from breakpoints) is added to the console.

  When you attach to a process, the program output is not redirected and only the debugger output is shown in the debugger console.

• Threads: displays the list of live threads and lets you switch between them. From this tab, you can export threads information in text format.

• Memory: provides the information on the currently available objects on the heap and lets you monitor and analyze their lifetime.

• Overhead: lets you monitor the resources consumed by particular debugger features and optimize the debugger performance.