-
Notifications
You must be signed in to change notification settings - Fork 752
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
debug: Ability to see the content of machine registers when debugging .s files #1527
Comments
That's a good idea. But ideally, I hope we can see the list of registers (maybe through the VARIABLES viewlet when we stop at .s?). |
I chat with @suzmue and @polinasok. Something to think about:
|
I'm on latest golang and delve, but I still cannot see the content of all registers. I can type XMM0, R15, etc in debug console and it would print a content of a register. But it cannot print XMM16 and above, YMM, ZMM, and K registers. In my settings, I have:
But I still don't see any content of registers anywhere. Is there a plan to fix this somehow? |
Currently the value from the settings is not correctly passed through to the launch configuration. Will send a fix for this. If you add "showRegisters": "true" to your launch configuration instead, it should work to display the register values. |
Change https://golang.org/cl/365374 mentions this issue: |
@suzmue That's a good tip, thanks :) BTW I really enjoy the feature to run a specific test in a .go file, which doesn't really have a launch configuration at all. I wish this worked so I could just click on tests I want to debug like that :) |
Update the list of delveConfig properties to merge. Updates #1527 Change-Id: I52ca4657a5323f68f5b6178b3676510d0870365f Reviewed-on: https://go-review.googlesource.com/c/vscode-go/+/365374 Trust: Suzy Mueller <suzmue@golang.org> Run-TryBot: Suzy Mueller <suzmue@golang.org> TryBot-Result: kokoro <noreply+kokoro@google.com> Reviewed-by: Hyang-Ah Hana Kim <hyangah@gmail.com>
The Go Nightly version includes Suzy's change. Would be nice if you can give it a try and verify it works. |
There is currently no way to inspect the content of machine registers. For example if you have some code written in go assemler (.s) file - you can step into that file and even hit a breakpoint, but you cannot see the content of registers, which makes debugging of such files kind of useless.
It would be nice to be able to see the content of machine registers at least in .s files.
The text was updated successfully, but these errors were encountered: