GoLand
 
2023.2
Shortcuts: Windows
Get GoLand
You are viewing the documentation for an earlier version of GoLand.
  1. Debugging
  2. Start the debugger session

Start the debugger session

Last modified: 20 July 2023

Starting a debugger session is very similar to running the program in normal mode. The debugger is attached behind the scenes, so you don't have to configure anything specific to start a debugger session. If you are able to run your program from GoLand, you will also be able to debug it using the same configuration.

note

This topic relies on your understanding of run/debug configurations. While GoLand provides a way to debug simple applications without any extra setup, understanding run/debug configurations is essential to efficient use of the debugger. More on them here.

Each time you debug a program, the debugger session is based on a run/debug configuration. Thus, you can configure GoLand to use any parameters and perform any actions before the program is launched. For example, the configuration can build the application every time you start a debugger session or use the previously compiled code.

Pause and resume a debugger session

When the debugger session is running, you can pause/resume it as required using the buttons on the toolbar of the Debug tool window:

  • To pause a debugger session, click the Pause button.

  • To resume a debugger session, click the Resume button F9.

note

Pausing the program manually is not an alternative to using breakpoints as this method doesn't let you use the full range of debugger functionality. For example, you cannot evaluate expressions after pausing the program.

Terminate a debugger session

  • Click the Stop button in the Debug tool window. Alternatively, press CtrlF2 and select the process to terminate (if there are two or more of them).

Productivity tips

Debug non-responding applications

In case your application hung, pause the session to let the debugger get the information about its current state. You can then examine the program state and locate the cause of the problem.

Do more with pause

When you need to evaluate an expression, and GoLand doesn't let you do that because you didn't stop at a breakpoint, you can advance your program a line further by stepping. After this, you will be able to use the debugger as if you had stopped at a breakpoint. While in some cases this may not be a valid solution, it may sometimes help you out.

Run before-launch tasks

Configure running external tools or performing other actions before every debugging session. This before-launch task can be running a Gulp or Grunt task or an NPM script, compiling your TypeScript code into JavaScript or running all the currently active File Watchers to compile or compress your code, uploading your sources to a remote server, and many more, depending on the language and frameworks you are using.

Before debugging

  1. Set breakpoints in the source code.

  2. If necessary, create or modify the corresponding Run/Debug configuration.

The debug session starts with the selected run/debug configuration. Note that several debug processes can be launched simultaneously.

tip

Alternatively, press AltShiftF9, select the configuration from the list, and press Enter.

See also

Reference