The photos below may not be completely up to date because the program is constantly being updated; try the latest build to see the updated interface.
This page gives a quick tour of the MemDBG frontend. Each section shows the main workflow exposed by the screen and the kind of console-side payload feature it drives.
The command center is the first operational view after launch. It summarizes the current console session, selected process, payload status, recent activity, and shortcuts to the workflows used most often during a debugging session.
The consoles screen manages direct payload sessions and discovery data. Use it to connect, ping, drop, or switch the active console endpoint without leaving the main interface.
The processes screen lists running targets and exposes their memory maps. It is the main place to select a PID, inspect mapped regions, filter maps, and prepare dump or scan ranges.
The memory screen provides direct read and write access for the selected process. It can inspect addresses, patch bytes, watch values, manage allocations, and scan selected maps for useful gadgets.
The scanner searches process memory for exact values and supports process-wide scans, explicit range scans, unknown-value sessions, and refinement passes such as changed, unchanged, increased, or decreased.
Pointer scan searches memory for addresses that reference a target address. It is useful when values move between launches or when building stable trainer entries from dynamic locations.
AOB scan searches for byte patterns with masks and wildcards. It is designed for signatures that survive address relocation and can be used to locate code or data patterns across a target process.
The trainer screen turns scan results or manual addresses into runtime cheat entries. Entries can be applied, restored, locked at an interval, imported from supported formats, and saved for later sessions.
The debugger attaches to a selected process and exposes thread control, register viewing/editing, breakpoints, watchpoints, step, stop, continue, and event polling for low-level runtime debugging.
Task Manager shows process state and per-process resource details. It helps compare memory maps, mapped memory totals, readable/writable/executable regions, and process control actions from one operational view.
UDP Logs displays payload log messages received over the UDP telemetry channel. It is useful for watching runtime errors, payload diagnostics, and console-side messages without interrupting the TCP command session.
Telemetry focuses on payload runtime counters: memory I/O, scan performance, packet sizes, cache behavior, and other metrics that help diagnose slow or unstable sessions.
Settings controls frontend defaults such as console IP, TCP/UDP ports, dump path, crash logging, language, and persistence. It is also where local configuration can be saved or restored.
Credits contains project information, license details, author links, and support links.
