Files
rpcs3/Utilities
caner 5ecfc95c13 Qt: add guest memory dump utility (#19068)
This adds a tool that writes a snapshot of the full PS3 guest address
space to disk for offline analysis.

This tool produces a flat image that any hex editor or script can index
directly by guest address. It dumps allocated PS3 guest memory only, not
RPCS3 host-process memory, host registers, or GPU-side state.

What it does:

1. Pauses emulation and waits up to five seconds for every PPU, SPU, and
RSX thread to settle. If they do not settle, nothing is written.
2. Copies every allocated guest page into an intermediate buffer on a
named worker thread, then writes it to a sparse `guest_memory.bin` whose
file offset equals the PS3 effective address. Reads go through
`vm::g_sudo_addr` so guest protected pages are captured too.
3. Saves each live SPU thread's 256 KB local store to its own file, with
its ID, LV2 ID, PC, and type recorded.
4. Writes `manifest.json`, listing every allocated region with its
addresses and permissions, the storage mode, and the SPU local-store
table.
5. Resumes emulation.

The menu entry is under Utilities next to Memory Viewer and is enabled
while a game is loaded. Free space is checked before writing. If sparse
file setup fails, the incomplete attempt is removed and the user can
choose another destination or cancel. Failed or cancelled dumps remove
their output folder instead of leaving a partial image.

Tested on Windows using an NTFS destination with a build from this
branch: dumped a running game with 479,535,104 allocated guest bytes
across 76 regions and five SPU local stores. The image was sparse, its
offsets matched guest addresses, and emulation resumed cleanly. The
sparse file failure path was also exercised with a temporary local test:
choosing another location reopened the destination picker, while
cancelling aborted the attempt without leaving partial output. Runtime
behavior on Linux and macOS is untested.

The first draft of this implementation was AI assisted. I reviewed and
adjusted the code and tested the Windows/NTFS path myself. I am happy to
rework anything or answer any questions.
2026-07-23 00:08:05 +00:00
..
2026-03-01 09:20:32 +02:00
2025-02-11 20:38:35 +01:00
2026-06-16 01:28:35 +02:00
2025-02-11 20:38:35 +01:00
2026-06-14 17:41:33 +02:00
2026-05-08 21:42:29 +02:00
2026-07-15 15:19:36 +02:00
2021-04-11 14:01:51 +03:00
2025-02-11 20:38:35 +01:00
2026-04-22 15:06:02 +02:00
2026-04-22 15:06:02 +02:00
2023-09-11 15:44:33 +03:00
2026-06-13 19:08:16 +02:00
2026-06-16 12:07:57 +02:00
2026-05-13 11:43:32 +03:00
2026-04-16 01:18:05 +02:00
2026-04-30 20:41:35 +02:00
2026-06-13 19:08:16 +02:00
2026-06-18 21:16:12 +02:00
2026-06-18 21:16:12 +02:00