Vscode-cpptools: [Feature Request] Memory viewer when debugging

[joshthielen]

Could you please add a memory browsing window to enable viewing of memory contents when debugging with gdb? It would also be great if the contents of watch variables / pointer locations could be easily shown in the memory browsing window (e.g. context-sensitive menu with 'View memory here').

[zhelnio]

I'm also waiting for this. The small workaround to watch one addr is to define memory pointer and add it to watching values. This is working for me.

[hoffmael]

This is a standard feature I look for in any debug GUI. It is extremely helpful to observe the data structure's memory as the code executes to get a full understanding of the system.

I hope this can be prioritized and implemented in a milestone soon

[doingnz]

yes please add this is a standard feature

[stuartthompson]

This would be a fantastic feature. This is the one reason I still run my code via gdb or lldb (depending upon which machine I'm working on) at the terminal instead of via vscode. Running exec x/ commands in the VSCode terminal just isn't an equivalent.

[hyt589]

Any updates on this feature?

[sean-mcmanus]

@hyt589 We don't currently have any plans to implement this.

If your host machine is Windows, you could use Visual Studio's memory/registers viewer when debugging on Windows or remote Linux targets: https://docs.microsoft.com/en-us/cpp/linux/deploy-run-and-debug-your-linux-project?view=vs-2019.

[andicam76]

Please add this to the roadmap! That's a standard feature to debug in embedded systems with gdb. When developing my projects with VSCode, I still need to run eclipse in parallel for debugging because of this missing feature.

[ghost]

I too would love this feature :heart:

[Trass3r]

For reference, here's the DAP spec change: https://github.com/microsoft/debug-adapter-protocol/pull/50
WIP implementation: https://github.com/microsoft/MIEngine/issues/816#issuecomment-661945883

[HuskyNator]

@hyt589 We don't currently have any plans to implement this.

If your host machine is Windows, you could use Visual Studio's memory/registers viewer when debugging on Windows or remote Linux targets: https://docs.microsoft.com/en-us/cpp/linux/deploy-run-and-debug-your-linux-project?view=vs-2019.

I might as well not use vscode and use visual studio instead . . . pretty disappointing.
I heard similar views when searching for a way of profiling, with many referring to visual studio 😕

[WardenGnaw]

We are investigating ways to add a memory view to this extension using the VS Code Hex Editor

[Danvil]

Ran into the same problem. For others who are stuck here: I am using a program called "Cheat Engine" in the meantime to look at disassembly and memory. It can connect to a running process and has a nice memory and disassembly. I copy the memory addresses from my VS Code debugging session over and can look at the memory (Ctr+G to jump to address).

[EmbeddedBacon]

@Danvil, thanks for the info on Cheat Engine. Looks promising, but looks only to support Windows an Mac, unfortunately not Linux. Still going to check it out though, thanks.