-
Notifications
You must be signed in to change notification settings - Fork 28.8k
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: Function Names not Visible in the Call Stack View #178964
Comments
Tagging @roblourens since this is close to #178308. |
Please file this on the repo for the Go extension. I think that the extension should either change what it is sending as the frame name (I'm not a Go expert so I'm not sure how to interpret what I see in your screenshot) or they can suggest a helpful way for us to truncate stack frame names in the UI that would preserve the most helpful info. |
Just to avoid any mistakes, this is a 22s video, can you confirm that you saw what the stack trace looked like towards the end, when the Call Stack View was much wider? Either way, I now passed this on to what I believe might be the right place: go-delve/delve#3323 |
I see it, but vscode only displays what the extension sends us, and it sent us a really long name |
Is there a way in the protocol to do this? |
Does this issue occur when all extensions are disabled?: N/A The issue is with the bundled call stack view (see attached movie clip), but I have to have the Go extension enabled to demo it with Go code and show the issue.
Steps to Reproduce:
I would prefer if function names were visible in the call stack view without having to make the side bar really really wide.
Demo
wide-or-unreadable-call-stack.mov
The text was updated successfully, but these errors were encountered: