-
Notifications
You must be signed in to change notification settings - Fork 8
Description
Describe the bug
When using the Memory View extension, selecting the 2-byte, 4-byte or 8-byte format in the Memory View causes some memory values to display as dashed lines (--) instead of actual values. The 1-byte format displays all values correctly. This issue occurs consistently during debugging sessions, making it difficult to inspect memory in2-byte, 4-byte or 8-byte formats.
To Reproduce
Steps to reproduce the behavior:
- Install the mcu-debug.memory-view extension in Visual Studio Code.
- Start a debug session using a debugger (e.g., Cortex-Debug with an STM32 microcontroller).
- Open the Memory View via the Command Palette (MemoryView: Add new memory view...) or by entering a URI (e.g., vscode://mcu-debug.memory-view/0x20000000).
- Enter a valid memory address (e.g., 0x20000000 for SRAM on STM32).
- Change the format to 2-byte, 4-byte, or 8-byte using the dropdown or settings in the Memory View.
- Observe that the 2-byte format shows all values, but 4-byte and 8-byte formats display dashed lines (--) for some or all values.
Expected behavior
All memory values should display correctly in 2-byte, 4-byte, and 8-byte formats without dashed lines, assuming the memory address is valid and accessible
Screenshots

Environment (please complete the following information):
- OS: Windows 11
- Version of Memory View (this extension) :0.0.27
- Debugger Type : cortex-debug
- Debugger Version :1.12.1
Additional context
The problem is consistent across debug sessions and persists after restarting VS Code.