Skip to content

eclipse-cdt-cloud/vscode-memory-inspector

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Folders and files

NameName
Last commit message
Last commit date
Feb 10, 2024
Jan 25, 2024
Dec 12, 2022
Mar 12, 2024
Mar 12, 2024
Dec 12, 2022
Dec 9, 2022
Oct 19, 2023
Oct 18, 2023
Dec 9, 2022
Dec 9, 2022
Dec 8, 2022
Feb 13, 2024
Mar 12, 2024
Mar 12, 2024
Jan 29, 2024
Mar 12, 2024

Repository files navigation

Memory Inspector

This extension contributes a set of widgets for viewing memory in different ways.

Requirements

This extension must be used in conjunction with a Debug Adapter that implements a ReadMemoryRequest handler or alternative custom request that returns memory data. It has been tested against the CDT-GDB Adapter used as the backend for the CDT-GDB VSCode plugin.

The Memory Provider

The primary entry point for the backend functionality of the plugin is the the MemoryProvider class. That class has two primary functions: it handles requests that are specified by the Debug Adapter Protocol, and it instantiates custom handlers that can provide additional functionality depending on the capabilities of a given debug adapter. In order to register custom capabilities, the AdapterRegistry matches debug types to objects implementing the AdapterCapabilities interface.

The Widgets

Memory Widget

The basic MemoryWidget class is a wrapper around two functional widgets, a MemoryOptionsWidget and aMemoryTableWidget. The MemoryOptionsWidget is responsible for configuring the display and fetching memory, and the MemoryTableWidget renders the memory according to the options specified by the user in the MemoryOptionsWidget. The basic combination of these three classes offers variable highlighting, ascii display, and dynamic updating in response to events from the debug session, as well as the option to lock the view to ignore changes from the session.