Debug tool window

If you run several debug sessions simultaneously, they are separated into tabs in the top part of the Debug tool window.

All the information in the editor, 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.

When you close a tab, the corresponding debug session terminates.

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

• Frames: use this pane to navigate in call stacks and switch between threads when debugging a multiprocess Node.js application or Service Workers.

  

• 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 client-side applications, the tab also shows everything that was logged in your code (for example, using console.*) and behaves also as a read-eval-print loop (REPL) so you can run JavaScript code snippets in it and interact with the page that you are currently debugging. Learn more from Interactive debugger console

• Process Console: WebStorm 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.*. Learn more from Using interactive Debugger Console.

  

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

  Learn more from Using interactive Debugger Console.

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

• Elements: this tab shows the actual HTML source code and the HTML DOM structure of the active browser page. Use the tab to monitor the changes made to the page through the browser.

  The tab is available only when you are debugging client-side code.

The debugger toolbar contains the most commonly used actions for controlling the debugger session and stepping.

You can configure the list of actions available on the toolbar according to your preferences.