Debugger not hitting breakpoints #1987
Comments
|
I think I'm seeing the same. In my case, my breakpoint appears to be hit - the program pauses, the callstack for my function says "PAUSED ON BREAKPOINT", but the I click on that thread it doesn't open the stack and shows no variables. I can continue the program and the thread goes back to "RUNNING" state, but that's all I see. I'm using go 1.11, vscode 1.28.0. |
|
I just started having this issue too. It started yesterday and I believe there was a VSCode update (and maybe an extension update?). As @youngderekm stated, it seems to hit the breakpoint, but nothing shows in the stack, the variables sometimes show (about 10% of the time I try to debug). One thing to note. If I have a previous breakpoint, somewhere BEFORE the GRPC endpoint gets hit, the debugger works correctly, but still does not show any debugging info for the breakpoint in question. For example: If I am inside of a GRPC func _ResourceClassification_GetClassificationType_Handler(srv interface{}, ctx context.Context, dec func(interface{}) error, interceptor grpc.UnaryServerInterceptor) (interface{}, error) {
in := new(GetClassificationTypeRequest)
if err := dec(in); err != nil {
return nil, err
}
if interceptor == nil {
return srv.(ResourceClassificationServer).GetClassificationType(ctx, in)
}
info := &grpc.UnaryServerInfo{
Server: srv,
FullMethod: "/<REDACTED>.ResourceClassification/GetClassificationType",
}
handler := func(ctx context.Context, req interface{}) (interface{}, error) {
>>>> return srv.(ResourceClassificationServer).GetClassificationType(ctx, req.(*GetClassificationTypeRequest))
}
return interceptor(ctx, in, info, handler)
}Verbose logs from the debugger is attached. The last few lines includes me stepping into the function that is failing. |
|
I see these errors in the VSCode Developer Tools console which seem to be related: |
|
@youngderekm I am seeing the same error too. Also see this in the Output > Log (Window) |
|
I have the same issue. Going back to vscode 1.27 (August) solved it for me. |
|
I have the same issue. Using Go 1.11.1 and vscode 1.28.1. |
|
Assume you downloaded from here? |
|
@sjdweb yes (well, in fact I still had a local copy) |
|
Any workaround available? |
|
BTW such behaviour occurs with projects outside $GOPATH/src/ |
|
I guess problem with this commit |
|
Still happening for me on the latest build. |
|
So the reason is that RPC return |
|
Here is pull request, please dont blame on me if this is not correct way to resolve the problem, but it works for me #2029 |
|
The bug has been fixed upstream and is available in the latest Insiders. Can folks here try the latest Insiders and share if the issue is resolved or not? |
|
I can confirm this appears to be fixed in the latest insiders! |
|
@freezlite's fix is now out in the latest update to the Go extension (0.7.0) |
|
@ramya-rao-a "Now out" or "not out"? In the last release? 😅 |
|
@jpeletier "now" out for sure :) |
|
I always have this error a few time aog with Go extension(0.7.0) |
|
And on my call stack i can see an error |
|
This not work on main vscode version with this error: |
|
@sebglon The errors you are seeing are not related to the current issue. Please log a new issue with these details along with a sample code where you see the issue |
If this is a bug report, please share
launch.json
Steps to Reproduce:
Adding a breakpoint when running
Output:
Adding a breakpoint before running debug
^ I can click the top of the callstack which will then allow me to continue, but at no point does this become an interactive debug. I can see locals like so:
Output:
The text was updated successfully, but these errors were encountered: