Debug process fails to start in Test mode as unable to find __debug_bin file #1701
Comments
|
@pantelis-karamolegkos Thanks for filing an issue! It looks like there may be two debug servers running, the Could you share the client side debug output as well (Command Palette -> "View: Toggle Output" -> Select "Go Debug" from the dropdown menu)? If you could include the launch request as well that would be super helpful, though I understand it may need to be sanitized to do so. |
suzmue
added
WaitingForInfo
|
@suzmue if you mean the Output in the attached screenshot, it is empty. Also, if by "launch request" you mean the
|
Could you make sure that Go Debug is the selected output channel? With "trace": "verbose" there should be logging there.
In the debug output it looks like there are a couple of lines which were removed. Specifically the launch request appears to be missing. It should look like: |
|
OK I see what you mean. Yes there is logging but that's a lot of stuff to sanitise ... :( I will try to find the time to post the info. |
|
Same problem here, if you dont mind me hijacking the response - here is the verbose log from the debugger with my comments: my launch settings: System: win10 |
|
@pantelis-karamolegkos Are you still experiencing this problem? Unfortunately, I am unable to reproduce it. The logs that you posted seem rearranged in an on odd way, so I am wondering if you accidentally combined the logs from two different runs. Could you also please use
Does this reproduce without the sensitive variables that complicate the logs?
Unlike Debug Console that is refreshed for every session,Go Debug channel accumulates logging from all sessions. You can clear it with this button before thee run where you want to inspect the log. |
|
@neozumm The original issue refers to inability to start up the binary ( This is a known issue on Windows due to how resources are released by the underlying systems. There is already a delay in the delve code to address this, but looks like it might not always be enough: |
|
Since I am still experiencing this issue, would removing / reinstalling the utility performing the debug be an option? I assume this is it? What is the recommended way of re-installing it? |
|
At least I have managed to change the error message... This This fails (notice that the only change is on the
trace logs |
|
@pantelis-karamolegkos I am able to reproduce this error message by attempting to launch a debug session for a folder that has no tests. Are there any test files in your workspace root? This error message is definitely very unclear so that needs to be improved. |
|
I assume the value of If so, no, there aren't. What value should I use for Thanks. |
|
The debugger is not currently able to handle running multiple test packages, because it is expecting to build and launch a single package. If you want a single launch configuration to run the tests in the directory of the file you currently have open, you can use: If you are just looking to run all of the tests in your package, I would recommend using the Test Explorer, using the commands |
|
update: All ok now :) Many thanks for the support 👍🏻 |
What version of Go, VS Code & VS Code Go extension are you using?
go versionto get version of Go from the VS Code integrated terminal.gopls -v versionto get version of Gopls from the VS Code integrated terminal.code -vorcode-insiders -vto get version of VS Code or VS Code Insiders.Go: Locate Configured Go Toolscommand.(check at the end of the issue)
Share the Go related settings you have added/edited
Run
Preferences: Open Settings (JSON)command to open your settings.json file.Share all the settings with the
go.or["go"]orgoplsprefixes.Describe the bug
Debug in test mode fails to run with message described below
Steps to reproduce the behavior:
I am hitting the
Debugbutton inVSCodeand select theTestmodewith the following configurations being available
and for the first time in my life I get the following error:
(when selecting the
Debugmode the process seems to be working as expected)Screenshots or recordings
If applicable, add screenshots or recordings to help explain your problem.
Debug output
(omitted the line with the env vars, containing sensitive info and was too large to filter out appropriately)
Go configuration tools
The text was updated successfully, but these errors were encountered: