You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.
My OS: Windows 10 x64
VSCode version: 1.36.1
Go extension version: 0.11.4
Golang version: 1.12.6
At the end of my application I have the following code:
If I run it outside the VSCode I can press Ctrl+C to terminate my application gracefully.
But if I run debug session in VSCode (via F5 button) my app runs in debug console and Ctrl+C doesn't work.
PS: and I'd like that pressing "Stop debug" button (Shift+F5) behaves as described in issue #2387
The text was updated successfully, but these errors were encountered:
Are you saying that you prefer the current behaviour of "Stop debug" button or you would prefer the fix for the issue #2387
I mean that first click sends TERM signal (and my application will try to process this signal). The second click does a force kill my app. Ideally, this behavior must be a configured option (to send or not to send the TERM signal on first click). IMHO )
My OS: Windows 10 x64
VSCode version: 1.36.1
Go extension version: 0.11.4
Golang version: 1.12.6
At the end of my application I have the following code:
If I run it outside the VSCode I can press Ctrl+C to terminate my application gracefully.
But if I run debug session in VSCode (via F5 button) my app runs in debug console and Ctrl+C doesn't work.
PS: and I'd like that pressing "Stop debug" button (Shift+F5) behaves as described in issue #2387
The text was updated successfully, but these errors were encountered: