mirror of
https://github.com/Dingo-Shenanigans/ReSkate.git
synced 2026-10-24 06:26:13 +02:00
AyeZeeBB
3249f747dc
Most crashes are caught by the game's own fatal handlers, which write a dump of thread stacks only; the launcher could only copy it after the game had exited. A crash on a freed or overwritten object then showed the faulting registers but not the object or the list it came from. - game_fatal_dump: the game's MiniDumpWriteDump import points at ReSkate. Before the game writes its dump, the crash reporter takes its own of the still-running game for the faulting thread; the game's dump follows as before. Reports say capture.source "game-fatal-handler". - The reporter's dumps include the memory the stacks point at (MiniDumpWithIndirectlyReferencedMemory), a few MB more a report. - The shared report says who asked for the dump (protocol version 4). - Tests: a game-handler crash is captured with a heap block only its stack points at; ReSkate's own capture keeps it too.
16 lines
884 B
C++
16 lines
884 B
C++
// Reviewed native contract for supported_build::game_sha256 (September 29 2026).
|
|
// The game's fatal handlers catch most crashes themselves (ReSkate's last-chance filter never
|
|
// sees them) and write their own minidump, of thread stacks only, in-process: three callers
|
|
// (0x18e3ea1 "Frostbite MiniDump", 0x2d28c9d, 0x2d2bfee) through one import thunk.
|
|
#pragma once
|
|
#include <array>
|
|
#include <cstdint>
|
|
|
|
namespace dingosdk::game::build::v20260929::game_fatal_dump {
|
|
// MiniDumpWriteDump's import slot (api-ms-win-core-debug-minidump-l1-1-0.dll).
|
|
inline constexpr std::uintptr_t import_slot = 0x05feb2e0;
|
|
// The thunk every caller goes through: jmp qword ptr [import_slot].
|
|
inline constexpr std::uintptr_t thunk = 0x0546dbc6;
|
|
inline constexpr std::array<std::uint8_t, 6> thunk_bytes{0xff, 0x25, 0x14, 0xd7, 0xb7, 0x00};
|
|
} // namespace dingosdk::game::build::v20260929::game_fatal_dump
|