-
Notifications
You must be signed in to change notification settings - Fork 238
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
Comments
Come to think of it, Suggestions welcome. In the market place, it is called |
This is a very important function, I hope this function can be supported in the future |
Hi people, please vote for native extension supporting a user settable memory viewer. 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. |
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 priorityThis 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
The text was updated successfully, but these errors were encountered: