Please note that we are still in Preview mode. For those using the API, this can change in the near future as we refine our proposals but it is getting more mature as it is being used in other extensions.
- Editing
- ---Selection, copy &--- paste
- Apply settings to workspace/user/all-views beyond the current view
- Scrollbars: We are not happy about the scrollbars. While scrolling works with the track-pad or mouse-wheel, the scrollbars are not always visible. We hope to have proper scrollbars in the future and soon. The infinite scrolling makes scrollbars a bit tricky. Any help is appreciated if you are a HTML/CSS/React expert.
- Major change: Now, there is a way to launch this memory viewer directly from the Variable/Watch windows. For debuggers that provide memory references. Most C/C++ debuggers do. See #25
- In some cases address expressions were not being evaluated properly
- When copying, the last byte sometimes did not get copied
- Refresh not done when a breakpoint is HIT #16 Memory was not being updated when the transition from
stoppedto running tostoppedhappened very fast. We never noticedrunningtransition and it looked like we went from stopped to stopped. Thus, no auto-refresh occurred. Generally not a problem with MCUs but was an issue with native code running on fast computers. The debounce existed because the React framework could not handle fast transitions and caused shimmering/flickering. If you see the shimmering, please let us know. So, this fix should be considered experimental. - Good news is that we now have a few non-embedded users for this extension.
- Added setting
memory-view.trackDebuggersto add additional debuggers to track.
- Experimental: Added Rust Probe Debugger to the list of debuggers supported. https://github.com/probe-rs/probe-rs/tree/master/debugger
- Fix Issue#10 Misaligned rows when saving memory to file
- You can now use you mouse to select a range of cells using your mouse. A single left-click starts the selection and Shift-left-click will extend the selection
- You can also copy the values to the system clipboard using the standard keyboard shortcut or the right-click context menu. Sorry, no paste within the viewer yet -- as that requires editing capabilities in this extension.
- There is new button for the 'Copy' function as well. If you hold the Alt (Windows, Linux) or ⌥ (MacOS) it can copy
allto clipboard. If the debugger is paused, we will try to refresh any data that may not be visible. - There is a new button for Saving the contents to a file
- In all cases (copy to clipboard or file), the data is always saved in byte form regardless of the current view (4-byte or 8-byte)
- Fix for Issue#9 Data regions are not refreshed synchronously. Needed to force a refresh
- Fix for when you change the editor font size, the data rows were not being resized accordingly. The data rows are now a tiny bit more compact as well
- Partial fix for Issue#7 Not vertical layout friendly. We still have a big problem with the header not scrolling horizontally with the content but the content is no longer cut-off/shrunk/etc. Experts in CSS/HTML/React are welcome to help us. We will eventually get this right.
- Some minor changes to editing (sorry not ready yet but you can try editing) and tab navigation
- Fix for Issue#7. One consequence of this is that the vertical scrollbar may not be visible anymore because it is inside and to the far right. If you scroll right far enough, it is there. See note about scrollbars above
- Some minor changes to editing (sorry not ready yet but you can try editing) and tab navigation
- vscode command
mcu-debug.memory-view.addMemoryViewnow supports adding with expression and/or other options - Avoid duplicate views wither via URI or via mcu-debug.memory-view.addMemoryView. For something to be considered a duplicate, the expression has to match and if they exist as options, the workspaceFolder and the sessionName have to match. Other optional things are not compared.
- Fixed Issue#1 STM32 memory locations off by 10 bytes. Actually, it was off by 0x10 bytes, bug introduced when we did the display for 4 and 8 byte grouping.
- Initial release, moved from haneefdm/memview to mcu-debug/memview
- Initial release of most of the view settings. Applying settings more globally is not yet implemented -- until we finalize a per view set of settings.
- Introducing 4-byte and 8-byte grouping. However, these groupings, you will not get the Decoded bytes. Instead however, you will see 32-bytes of data per row whereas you see 16-bytes per row in 1-byte mode
- For 4-byte and 8-byte grouping, we also support little/big endian conversion
- The top-left of a memory view now shows the start-address of the view. Note that this is different from the base-address which is always a multiple of 16. So, you start-address and base-address can be slightly different and base-address <= start-address. The start-address will always be on the first row though.
