How to set up debugging in GoLand?

Question

I am trying out GoLand and hear that the debugger is supposedly awesome, but I can’t find any documentation explaining how to set it up (GoLand is in preview stage, so that’s no

Answer 1

I right click on project (main.go inside) and choose "Debug ..." and it work

Answer 2

On version 2019.1.1 there's no more Go Application. Use Go Build instead. Here I am debugging a single script file, but if you have a server app or smth, just point to the main app file:

Notice that in the Files field you have to specify the actual file path. You can put more files (if you want to have more starting points) by separating them with a pipe |. For each file you want to be able to debug, you need to specify the full path.

Again, if you are debugging a server app or something else, that has a single starting point, you only need the startup file specified in the config. :)

Answer 3

I had this exact problem.

Deleted and recreated the Debug run configuration. Debugging then worked perfectly.

Answer 4

I was facing this same issue and I solved by using the "Go Application" configuration (at the Run/Debug Configurations window), instead of the "Go Single File" configuration.

So, go to the upper right corner of the Gogland and "Edit configurations".

Then, add a new configuration using the "Go Application" profile.

After saving, you should be able to debug your code. o/

An easy way to enable this configuration is to use the @user1793301 method and right click on the file you want to run and select "Debug 'go run .go'".

---

POSSIBLE EXPLANATION

NOTICE: I did not look any further details about it.

Fact: "Go Application" configuration does build the binary executable before running it.

Fact: I could see looking at the console output (inside of the Goglang) is that the IDE uses the DLV as debugging tool.

Fact: I found a dlv debug at the DLV documentation and it seems to compile and debug the code.

Hypothesis: The guys from Jetbrains did not implement it. Or at least not YET.

Answer 5

GoLand will not enable the debug action (although run is available) if your code does not reside inside src. There is no warning about this, so it might be really a pain to solve this.

Additionally, depending on your project’s structure it might be possible, that debugging is still not working. In that case, it might help to remove all run configurations and create a new one. There’s is a bug report about this behavior.

PS: Although the OP mentions the first part in an edit of the question, but it think it’s worth mentioning in an answer.

Answer 6

Things changed in goland since @Jamillo Santos added his reply.

To start with, there's no more "Go Application".

The easiest way is to locate the file containing the main() function. There should be a small triangle pointing to it, like in the attached screenshot:

When you click on the small green triangle, you get a menu with Run/Debug options. Each will create a go build configuration.

You can edit that go build configuration and add the program arguments for your application. For example, if your program have a command line argument of --arg=value you can add it like this: