windows-dmp-analysis

Automate symbol matching and stack trace parsing for Windows crash dump files.

2.6k|191|Updated Apr 26, 2026

Search Tags:#stack-trace #dmp-analysis #crash-diagnosis #maante #maaframework #windows-debugging #dump-symbols

Ready to run

npx skills add https://github.com/1bananachicken/MaaNTE --skill windows-dmp-analysis-1bananachicken

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the tedious and expertise-heavy work of manually diagnosing Windows crash dump files for MaaNTE, which requires matching correct PDB symbols and parsing unreadable raw stack traces without specialized tooling.

Core Features & Use Cases

Automated Symbol Resolution: Automatically downloads matching PDB symbol files for MaaFramework and MXU versions detected from logs and issue metadata.
Full Stack Trace Analysis: Parses symbolicated stack traces to identify crashing modules, exception types, and root cause functions across MaaNTE's core dependencies.
Use Case: When a user reports a MaaNTE crash and attaches a .dmp file to a GitHub issue, use this Skill to run the full analysis workflow and generate a structured report with root cause judgment and fix recommendations for both users and developers.

Quick Start

Use the windows-dmp-analysis skill to analyze the crash.dmp file attached to issue #456 and produce a full crash root cause analysis report.

Frequently Asked Questions about windows-dmp-analysis

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

FAQPage Schema

How do I diagnose a MaaNTE crash from a Windows .dmp file?▼

To diagnose a MaaNTE crash from a Windows .dmp file, you can automate symbol matching and stack trace parsing to identify the crashing module and root cause. This process extracts version-matched PDB symbols from issue metadata to generate a readable stack trace.

How does automated symbol resolution work for MaaFramework crash dumps?▼

Automated symbol resolution for MaaFramework crash dumps works by detecting framework versions from logs and automatically downloading the matching PDB symbol files. This allows the system to parse raw stack traces and pinpoint the exact function causing the exception.

What is the best way to parse unreadable stack traces from MaaNTE GitHub issues?▼

The best way to parse unreadable stack traces from MaaNTE GitHub issues is to use an automated crash diagnosis workflow. It retrieves the correct MXU and MaaFramework PDB symbols based on issue metadata and outputs a structured analysis report with root cause judgments.

Can I analyze MaaFramework crash dumps without manually finding PDB symbols?▼

Yes, you can analyze MaaFramework crash dumps without manually finding PDB symbols. The analysis workflow automatically detects the required versions from log files and retrieves the exact matching debug symbols to symbolicate the stack traces.

What do I need to generate a crash root cause report for MaaNTE?▼

To generate a crash root cause report for MaaNTE, you need the attached .dmp file and the issue metadata from the GitHub report. The analysis uses these inputs to download dependencies, parse the exception type, and provide fix recommendations for developers.