[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.