закешированный к нам в целях безопасности дебаггер
![]() Using issue419.go, I observed that the continue command fails with an error when debugger receives and forwards an interrupt. In spite of the stopped event, vscode still shows the state as RUNNING because the threads request is unable to retrieve any threads, but at least one dummy thread is always expected. Co-authored-by: Polina Sokolova <polinasok@users.noreply.github.com> |
||
---|---|---|
_fixtures | ||
_scripts | ||
.teamcity | ||
assets | ||
cmd/dlv | ||
Documentation | ||
pkg | ||
service | ||
vendor | ||
.cirrus.yml | ||
.deepsource.toml | ||
.gitattributes | ||
.gitignore | ||
CHANGELOG.md | ||
CONTRIBUTING.md | ||
go.mod | ||
go.sum | ||
ISSUE_TEMPLATE.md | ||
LICENSE | ||
Makefile | ||
README.md |
The GitHub issue tracker is for bugs only. Please use the developer mailing list for any feature proposals and discussions.
About Delve
Delve is a debugger for the Go programming language. The goal of the project is to provide a simple, full featured debugging tool for Go. Delve should be easy to invoke and easy to use. Chances are if you're using a debugger, things aren't going your way. With that in mind, Delve should stay out of your way as much as possible.