Debugger memory views #133
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add system memory view for debugger. Under the Variables->System->Memory entry, can click on the icon shown when hovering to get memory view using VS Code's native view. A bit clunky but I don't see a more direct way to get it.
Also adds the ability to create watches with addresses directly, by placing the address within brackets, instead of a label or symbol name e.g.
(&1900).w to get the 16 bit word stored at 0x1900, formatted as a decimal value
$($80) to get the byte stored at 0x80
String formatting can now also be applied with the .sXX suffix, where XX is the number of bytes to read e.g.
somelabel.s8