-
Notifications
You must be signed in to change notification settings - Fork 646
Debug file not getting cleared after debugging on Windows #2265
Comments
this is normal, you cannot hide it however you can .gitignore it |
I think that's how delve works. |
We use delve to provide the debugging feature. |
I just run a hello word program,then this is my code:.vscode/launch.json {
"version": "0.2.0",
"configurations": [
{
"name": "Launch",
"type": "go",
"request": "launch",
"mode": "auto",
"program": "${fileDirname}",
"env": {},
"args": []
}
]
} src/main.go package main
import (
"fmt"
)
func main() {
fmt.Println("Hello word")
} The version infoVSCode version:1.30.2 Steps
|
When you have finished debugging, the file doesn't get cleaned up? |
Yes, the debug file has not been cleared. |
Thanks @monkeyWie I see this in Windows, but not on my Mac. |
@jhendrixMSFT This is most likely due to delve. By the time we send the Halt request to delve, delve has already completed running the whole program. So the Halt request fails with I would expect delve to clean up the debug file it created in such cases, we should look into why this is not happening as well as why it does happen on Mac |
@vladbarosan Right now we end up at https://github.com/Microsoft/vscode-go/blob/0.9.0/src/debugAdapter/goDebug.ts#L533 failing to halt delve because delve has already halted (sort of) I am not sure if the Halt request failed here or the Detach request. |
@monkeyWie The fix for this is available in the latest beta version of this extension. Please give it a try |
Thank you, I will try it when I have time. |
Bug has been fixed. |
@ramya-rao-a |
@monkeyWie Can you create a new issue for that? The fix that was put in place for this issue is out in the latest release(0.10.0) of this extension |
Is this normal?Can I hide it?
The text was updated successfully, but these errors were encountered: