-
-
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
Debugger not working on Windows #2511
Comments
I think this is a duplicate of #2481 . I don't have a window machine, but I'd love to get to the bottom of it. If anyone can help, I would surely appreciate it. |
It looks slightly different, but could still very well be the same. I am sadly not very knowledgeable when it comes to VIM and how to find these errors. Yet I am willing to help if there is anything I can do/try. Just let me know! |
what I really need is to figure out what delve is sending on Windows and why it's different than on other systems. Can you run vim with |
I hope this is what you are looking for. I did the following: I opened a file, set the current working dir to that files location. I tested the program with :GoRun, which works great. Then :GoDebugStart, :GoDebugBreakpoint, :GoDebugNext. Then the error happens...
|
Do you have the same problem if you run |
If I remember correctly there was no difference. I will try again a little later. Do you need the dump again? |
I don't need the dump again. |
Just checked. Exact same behavior. |
@thingsis the output I need is what's in |
Thanks, @thingsis. What I need is the value of |
@thingsis I've been able to figure out at least part of the problem and will be putting up a PR in the next couple of days to eliminate the errors you're seeing. |
RPC responses are sometimes empty on Windows, so check that the results are a dictionary and that the result field is not empty. Fixes fatih#2511 Fixes fatih#2481
@bhcleek I will try this today since I was travelling the last few days. I will post my feedback here later. |
@bhcleek At the moment the master branch doesn't seem to be in a state in which I could try this - getting errors as soon as I open go files or try to install the go binaries. I will wait till the next release and try again. |
I'm not aware of any issues on master similar to what you're describing. Please open a new issue if you need help or want to see them fixed. |
What did you do? (required: The issue will be closed when not provided)
Installed vim-go
Compiled and ran program with :GoRun (works)
Tried debugging with :GoDebugStart, :GoDebugBreakpoint, :GoDebugNext
What did you expect to happen?
The Program to be executed in the debugger as per the manual
What happened instead?
It throws error messages already when trying to create the breakpoint. Then gvim crashes when starting to debug.
Configuration (MUST fill this out):
vim-go version:
Did "git clone https://github.com/fatih/vim-go.git ~/.vim/pack/plugins/start/vim-go" today. How do I find out which version?
vimrc
you used to reproduce (use a minimal vimrc with other plugins disabled; do not link to a 2,000 line vimrc):vimrc
Vim version (first three lines from
:version
):VIM - Vi IMproved 8.1 (2018 May 18, compiled May 18 2018 18:36:07)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1
Go version (
go version
):go version go1.13 windows/amd64
Go environment
go env
Output:The text was updated successfully, but these errors were encountered: