debug-dumps
Skill1 starsChanged 11 days agoAGPL-3.0View on GitHub
Analyze and debug Windows crash dumps (.dmp) and app crashes for Agentmaster (the C++/WinRT WindowsTerminal fork) WITHOUT cdb/WinDbg — using the in-repo DIA-SDK + DbgHelp tools. Covers the whole loop: find the crash (WER Application Error event id 1000 + the full dump in %LOCALAPPDATA%\CrashDumps), read the exception record + faulting registers (dumpexc), decode what it means (0xC0000005 access violation, 0xC0000409 __fastfail incl. the CFG subcode 0xA freed-vtable, 0xC000027B stowed fail-fast, the 0xDDDDDDDD "dead-land" freed-memory register signature, non-canonical -1 faultData), walk the faulting-thread stack (dumpwalk2 ordered StackWalkEx; dumpourscan full-stack scan for OUR frames with a module histogram; dumpstack/hangwalk fallbacks), and symbolize OUR frames against the matching build's PDBs to pin the exact source line + root cause. Encodes the hard-won patterns: matching the PDB to the CRASHED binary by build time, "zero of our frames == a deferred/async XAML fail-fast off our call stack (uncatchable)", use-after-free of reused XAML peers, fire_and_forget std::terminate, iterator/UAF classes, and how a try/catch canNOT catch an AV (/EHsc) or a __fastfail (bypasses SEH). Includes a self-contained crasher (makedump) that generates a tiny, non-sensitive test dump reproducing the freed-fill AV signature, plus that compressed fixture (test/sample-crash.dmp.gz). Use whenever an Agentmaster (or any native Windows app) instance crashes, hangs, or fail-fasts, when asked to analyze a .dmp / minidump / WER report, find a crash's root cause, symbolize a fault offset, or reason about an exception code / access violation / stowed exception / __fastfail.
In this repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- build-installSkill
- claude-wrap-ConPTYSkill
- release-notesSkill
- release-versionSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 1 is distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.