-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
GoDebugTest fails #2002
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Comments
This should be fixed in #1992. Can you give it a try? |
I have the same issue. I will try the commit #1992 |
Sorry for the delay in responding. #1992 solves the issue. Is there some tutorial on how to use the GoDebug mode? |
The help file is currently the best resource for understanding the debugging feature. See |
Thanks a lot for your time, much appreciated! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What did you do? (required. The issue will be closed when not provided.)
I wanted to try the GoDebug* set of commands. I set a break point with
:GoDebugBreakpoint
in one if my unittested functions. Then i executed:GoDebugTest
.What did you expect to happen?
I expected to see some form of debugger i guess. I didn't know quite what to expect as i've not used the GoDebug* set of command before.
What happened instead?
This even though i have debugger installed, but it's installed in
/home/patriki/go/src/github.com/derekparker/delve/service/debugger
.Configuration (MUST fill this out):
vim-go version:
SHA-1: b6381dd
vimrc
you used to reproduce (use a minimal vimrc with other plugins disabled; do not link to a 2,000 line vimrc):vimrc content not relevant here i think.
Vim version (first three lines from
:version
):Go version (
go version
):go version go1.11 linux/amd64
Go environment (
go env
):The text was updated successfully, but these errors were encountered: