Replies: 1 comment 2 replies
-
That check was added as a workaround for #109 (microsoft/vscode-go#1383). Ability to use multiple debugging sessions is cool. I think more correct way to handle the original issue is to address only this specific case (debug session started with the test codelens). |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi all.
We have been using the VSCode Go extension (congrats for the integration) for several years now and for a couple of months, an issue impacts our debugging workflow.
We did not find any related issue on the subject and we are looking for advices here.
We use the following debugging pattern:
launch.json
Whereas it used to work (not sure exactly when it stops working), we now get the following error message ‘Debug session has already been started’.
As a (painful) workaround, we use the following pattern:
Since this works, since the “compounds” section of
launch.json
also works, there seems to be no limitation in debugging several processes at the same time.After a quick search, the culprit code seems to be located in
vscode-go/src/goMain.ts
Line 358 in 83aa2cb
The final question is: why is the vscode.debug.activeDebugSession flag taken into account when locally debugging a specific test?
Should there be a better place to ask, please redirect me to it!
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions