Memory Bridge Viewer

Inspect, edit, and compare memory while debugging in VS Code. The extension connects the active debug session to a bundled Windows x64 C++/ImGui viewer. It can also compare BIN files without a debug session.

Features

• Memory Viewer: Open multiple floating viewers, navigate by address or symbol, display 1/2/4/8-byte cells, and refresh visible data manually or automatically.
• Memory writing: Edit a cell in place. Writes use the debugger's supported path and are checked by reading the value back. An uncertain result prompts you to refresh before retrying.
• Compare Viewer: Compare two live memory regions, a live region with a snapshot, or two BIN files. BIN comparison adapts to the longer input file and highlights missing or changed bytes. Export a CSV difference report.
• Hover layouts: Import JSON field definitions or convert supported flat C structs to a hover config. Nested structs and unions are rejected with a clear error; invalid imports leave the current layout intact.
• Controller tools: Manage viewers, refresh open windows, pause or resume auto refresh, import named constants, switch themes, and adjust UI scale.
• Diagnostics: View startup, connection, read, and write details in Output → Memory Bridge Viewer.

The separate ImGui window contains the memory grids and tools. The Features tab in VS Code lists this extension's contributed Command Palette commands; the viewer controls are described here and in the manuals below.

Getting started

1. Install this Windows x64 VSIX in VS Code 1.90 or newer.
2. Start a debug session with a debugger that supports DAP readMemory. Pause the target and select a stack frame when reading symbols or writing memory.
3. Run Memory Bridge Viewer: Launch/Restart C++ Viewer from Ctrl+Shift+P, or use the Memory Bridge Viewer status bar item. The viewer may also open when debugging starts.
4. Enter an address in a viewer, click Apply, enable access, and click Refresh. Double-check the selected frame and address before editing a cell.

You can open the viewer before starting a debug session. Live memory access then waits for a compatible debug session. BIN comparison works independently of the debugger.

Command Palette commands

Requirements and dependencies

• Platform: Windows x64. The native viewer executable is bundled in the VSIX.
• VS Code: Version 1.90 or newer. The extension runs in the local UI extension host to launch its Windows executable.
• Live memory: A debug adapter with DAP readMemory support. Write support depends on the adapter; the extension uses native DAP writeMemory when suitable or an evaluate fallback, followed by readback verification.
• Other VS Code extensions: None are declared as mandatory extension dependencies. Install the debugger extension appropriate for your target separately.
• Bundled runtime components: The ws Node.js package and native viewer dependencies ship inside the VSIX. They do not appear in VS Code's Dependencies tab, which lists other VS Code extensions required by this one.

Documentation and troubleshooting

Press Ctrl+Shift+P, run Memory Bridge Viewer: Open User Manual, and choose 繁體中文 or English. The bundled manuals cover viewer controls, comparison modes, hover configs, C struct importer limits, writing, and troubleshooting.

If the viewer does not open, stays black, or cannot read memory, open Output → Memory Bridge Viewer. The startup log shows the extension version, executable path, file size, debug session, and connection state. Check that the target is paused, a frame is selected, and the debugger supports memory reads.

License

Copyright (c) 2026 LunarCub Forge. Memory Bridge Viewer is proprietary software; see LICENSE.md in the extension package. Open-source components retain their own terms; see THIRD_PARTY_NOTICES.md and its accompanying license files.