-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
GoDebugTest freezes nvim #2123
Comments
@akupila Thank you for the bug report. You identified an issue where Neovim could sometimes lock up. That's been resolved in #2125. Without a package argument, both |
Oh, i completely missed that part in the doc. Thanks for the response! However, i would probably interpret Confirmed your fix to the lock up works (although it's a bit strange to the user since there's no feedback) |
What did you do? (required. The issue will be closed when not provided.)
I attempted to debug a test with
:GoDebugTest
but neovim froze.I did some digging and found that delve is not started with the correct package. If my project root is
github.com/a/b
, i opengithub.com/a/b/mypkg
and attempt to debug it there, delve is started withgithub.com/a/b
as the package. I found this by modifyingdebug.vim
to print the package:The strange thing is that it did sometimes work correctly, without any (known) changes from my side. Still, this occurrence was rare and i've not been able to pin point any specific action i took to make it work.
:GoDebugStart
works fine but it's different because it doesn't target the sub package. Also, explicitly passing the package works::GoDebugTest github.com/a/b/mypkg
.Here's a repro repo: https://github.com/akupila/vim-go-debug
What did you expect to happen?
Delve should start and debug UI open, as with
:GoDebugStart
What happened instead?
Neovim freezes (not able to get it to respond to any input)
Configuration (MUST fill this out):
vimrc
you used to reproduce (use a minimal vimrc with other plugins disabled; do not link to a 2,000 line vimrc)::version
):go version
):not applicable
go env
):not applicable
The text was updated successfully, but these errors were encountered: