Skip to content
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

Announcement: Better memory viewer on the way #729

Closed
haneefdm opened this issue Aug 28, 2022 · 3 comments
Closed

Announcement: Better memory viewer on the way #729

haneefdm opened this issue Aug 28, 2022 · 3 comments

Comments

@haneefdm
Copy link
Collaborator

haneefdm commented Aug 28, 2022

Hi Folks,

We may have a better memory viewer soon. It is in preview right now and will be integrated into Cortex-Debug soon. I did it as a separate extension so it can work with all debuggers that need to deal with memory. Not limited to embedded Cortex-M. Even with it not integrated you can use it as is -- just a different command from the Command Palette

https://marketplace.visualstudio.com/items?itemName=mcu-debug.memory-view
https://github.com/mcu-debug/memview

I think it will be better than what we have right now, supports very large (but artificially limited to 1MB) memories while fetching only what is needed. The memory views also survive a VSCode restart.

You may ask "what about Hex Edittor" which is already integrated into VSCode (especially into Variable and Watch windows). While it may be great for files, it does not play nice with a debugger with memory contents always changing and other issues documented here. If you like Hex Editor, by all means, keep at it. If you see their issues list, working well with a debugger is not a priority

This document also captures my design intent and why I am doing it in the first place. I will move this document to the memview extension shortly.

If you like this, come help me by trying it out. More importantly, I am going to be asking Microsoft to integrate this type of memory view by providing a setting and your support will be key. Right now, for Variable and Watch windows, they hard coded it to the Hex Editor and we should have a choice. They also use a URI mechanism but not one that is friendly to other extensions.

Please see #729 (comment) and upvote on the MS website

@haneefdm haneefdm pinned this issue Aug 28, 2022
@haneefdm
Copy link
Collaborator Author

Come to think of it, memview is perhaps a bad name. There seems to be some other software named similar but it is not a VSCode extension.

Suggestions welcome. In the market place, it is called MemoryView

@hongshui3000
Copy link

NOTE: Editing features are not yet ready for use. You can edit but the edits will not be saved to your program

This is a very important function, I hope this function can be supported in the future

@haneefdm
Copy link
Collaborator Author

Hi people, please vote for native extension supporting a user settable memory viewer.

microsoft/vscode#155597

If they don't see 20 votes, they will just close it. I found out today, but that was posted a long time ago. Click on the thumbs up reaction for the first post.

Sadly, we have less than two weeks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants