Debug tool window

Sessions

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

Tabs

The Debug tool window shows the following tabs and panes for each session:

• Threads & Variables: this tab comprises several panes that display information about threads, frames, watches, and variables.

  

  • Threads: displays the list of live threads and lets you switch between them.

  • Frames: lets you navigate in call stacks of the threads.

  • Watches: lets you manage watches.

  • Variables: lists the variables available in the current context and lets you analyze and modify the program state.

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

• Process Console: Aqua opens this tab when you are debugging a Node.js application. The tab shows the output of the node process itself, that is, everything that is written to process.stdout and process.stderr directly or is logged using console.*.

  

• Debugger Console: Aqua opens this tab when you are debugging a Node.js application. Here you can run JavaScript code snippets and view the console.* messages.

  

• Scripts: during a JavaScript debugging session, the tab shows all the external resources that are automatically downloaded during the JavaScript code execution. Use this tab to monitor downloading the external resources. To open the code of a resource in the editor, double-click the item in question.