Delve error when debugging test with 2018.1 EAP on Go 1.10 rc1
After upgrading to Go 1.10rc1, I can no longer run with debugger attached. I get the following error:
could not launch process: could not find .debug_frame section in binary
I realize this is a Delve error, but is anyone else running Goland 2018.1 EAP running into the problem? I am unsure if this is something with my local setup or a known issue with the version shipped with Goland.
Please sign in to leave a comment.
Hi, can you please add more details about this issue?
What are:
- the operating system and version
- what are the setup commands the IDE runs in order to run the configuration. They should be in the Run output, collapsed by default with the text "<4 go setup calls>" and paste the output here.
If you compile the binary yourself, please describe how you are doing it and how you are attaching delve to it. Also, if you are not using the delve version shipped with the IDE, please make sure you've downloaded the latest Delve version and compiled with Go 1.10 RC1.
Sure; OS is Fedora 26.
The setup commands are as follows:
I am using the Delve version shipped with the IDE, using the Go 1.10 rc1 version provided here (not compiled locally). I am running this by right clicking on the _test file in Goland and clicking "Debug 'x_test.go'"
Thanks
I've had a brief look at this and it seems to be caused by the fact that the project is using the ` plugin ` package which is not currently supported by delve. I cannot confirm 100% just yet but I'll try and do so soon. Sorry for the delay.
Thanks for taking a look. That is interesting! You are right that ripping out any mention of the plugin package allows me to debug. It is sort of weird though that this has been working fine this entire time and just started recently; I wonder if this is specific go Go 1.10 rc; I can try to repro the behaviour with 1.9 later today and maybe then find out if this needs to be reported to Delve or Go maintainers.
Fyi after confirming that this works fine on Go 1.9 with a really simple repro, I have filed a Delve issue: https://github.com/derekparker/delve/issues/1118