Closed
Description
- VSCode Version: Code 1.13.1 (379d2ef, 2017-06-14T18:13:05.928Z)
- OS Version: Darwin x64 16.6.0
- Extensions:
Extension | Author | Version |
---|---|---|
aurelia | AureliaEffect | 0.3.4 |
vscode-npm-script | eg2 | 0.2.0 |
task-master | ianhoney | 0.1.39 |
quicktask | lkytal | 2.8.0 |
Go | lukehoban | 0.6.62 |
debugger-for-chrome | msjsdiag | 3.1.4 |
Steps to Reproduce:
- Open a Golang project
- Debug something
- Stop debugging (via
Stop
, aka the red square or Shift+F5)
delve
is the debugger for golang, or at least it's the one that the Go extension uses. When you debug something with delve, it creates a large binary file in the current directory. If you debug a main function (dlv debug
), you get 'debug'. If you debug a test function (dlv test
), you get 'debug.test'.
In normal delve
usage, when you're done, you quit
delve. Delve then deletes this file. Apparently VSCode gracelessly terminates (SIGKILL?) delve, which means the file sticks around.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Metadata
Assignees
Labels
No labels