Description
Live Watch, Component Viewer, and Core Peripherals can be affected by changes to memory, for example when executing script/CLI commands, editing variable values, etc.
In such case, the debug adapter announces changes through DAP events (invalidate, memory, and others).
We need to handle typical events that trigger VS Code (debug view) refreshes.
Steps to Reproduce
- Connect to a target application
- Chose a global variable known to live in memory, e.g.
SystemCoreClock in many CMSIS examples or osRtxInfo in RTX examples.
- Add the variable to Watch and Live Watch. Note that some fields of
osRtxInfo are also shown in the SCVD description for RTX.
- Modify the value through variables/expressions/CLI commands like
set (note that the GDB memory notification warnings will go away soon).
You should notice that the variable Value in the Watch window changes, while it doesn't in the Live Watch. Same with Component Viewer if you modify something in osRtxInfo.
Expected Behavior
Changes to memory by modifying variables should refresh potentially affected windows.
In the long term, the same should happen when modifying memory. But this requires the fix for #974 to be published first. Provisions could be done already today though with a local build of that.
Additional Information
No response
Description
Live Watch, Component Viewer, and Core Peripherals can be affected by changes to memory, for example when executing script/CLI commands, editing variable values, etc.
In such case, the debug adapter announces changes through DAP events (
invalidate,memory, and others).We need to handle typical events that trigger VS Code (debug view) refreshes.
Steps to Reproduce
SystemCoreClockin many CMSIS examples orosRtxInfoin RTX examples.osRtxInfoare also shown in the SCVD description for RTX.set(note that the GDB memory notification warnings will go away soon).You should notice that the variable Value in the Watch window changes, while it doesn't in the Live Watch. Same with Component Viewer if you modify something in
osRtxInfo.Expected Behavior
Changes to memory by modifying variables should refresh potentially affected windows.
In the long term, the same should happen when modifying memory. But this requires the fix for #974 to be published first. Provisions could be done already today though with a local build of that.
Additional Information
No response