windows-dmp-analysis

Name: windows-dmp-analysis
Availability: InStock
Author: MaaEnd

Analyze Windows minidump files to diagnose MaaFramework or MXU crashes.

3.6k|298|Updated Mar 18, 2022

Search Tags:#symbolication #minidump #dmp-analysis #windows-crash #stack-walk #pdb-symbols

Ready to run

npx skills add https://github.com/MaaEnd/MaaEnd --skill windows-dmp-analysis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: windows-dmp-analysis
Source: https://github.com/MaaEnd/MaaEnd/tree/main/.claude/skills/dmp-analysis
Command: npx skills add https://github.com/MaaEnd/MaaEnd --skill windows-dmp-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze Windows minidump (.dmp) files to diagnose MaaEnd crashes and their dependencies (MaaFramework and MXU), locating root causes using symbol information and automatically fetching PDBs from GitHub Releases. It leverages minidump-stackwalk to produce readable stack traces and helps triage issues involving MaaEnd, MaaFramework, and MXU.

Core Features & Use Cases

Obtain and analyze Windows .dmp files to identify crash origins and implicated modules.
Download and apply PDB symbols from GitHub Releases to enable accurate symbolication.
Produce a structured crash report with versions and suspected components for faster debugging.

Quick Start

Download the .dmp file and run minidump-stackwalk to generate a symbolicated crash report for MaaFramework or MXU.

Frequently Asked Questions about windows-dmp-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I analyze a Windows minidump file to find the root cause of a crash?▼

You analyze a Windows minidump by running minidump-stackwalk against the .dmp file, fetching PDB symbols from GitHub Releases to generate a symbolicated stack trace that identifies crash origins and implicated modules.

How does symbolication work when debugging a Windows .dmp crash dump?▼

Symbolication works by downloading PDB symbols from GitHub Releases and applying them to the minidump-stackwalk output, translating raw stack memory addresses into readable function names and stack traces for accurate root cause diagnosis.

Can I use this crash analysis process for aarch64 Windows dumps or is it only for x86_64?▼

Windows crash dump analysis primarily targets x86_64 dumps, but aarch64 dumps are supported by adapting the configuration and changing the PDB symbol URLs to fetch the correct architecture-specific symbols.

What do I need to diagnose MaaFramework or MXU crashes on Windows?▼

To diagnose MaaFramework or MXU crashes, you need the Windows .dmp file, minidump-stackwalk, and dump_syms tools, which automatically fetch PDB symbols to output a structured report detailing versions and suspected components.

Why does my Windows crash dump show unresolved stack frames instead of function names?▼

Unresolved stack frames occur when PDB symbols are missing or not applied; fetching the correct PDB symbols from GitHub Releases and running them through minidump-stackwalk translates memory addresses into readable function names.