symbolicate-crash-dump
SolidSymbolicate a native VS Code crash dump (.dmp) using electron-minidump. Use when given a crash dump file, asked to symbolicate a crash, resolve missing method names in a native crash backtrace, or attach Electron/Insiders/Stable symbol files. VS Code team members only; requires macOS or Linux.
Install
Quality Score: 82/100
Skill Content
Details
- Author
- chapmanjw
- Repository
- chapmanjw/clawdius
- Created
- 2 months ago
- Last Updated
- 5 days ago
- Language
- TypeScript
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
xcsym
Symbolicate and triage iOS/macOS crash reports (.ips, MetricKit, legacy .crash, Xcode Organizer .xccrashpoint) via the `xcsym` CLI. Use when given a crash file to diagnose, when TestFlight/App Store Connect crashes need triage, when a crash comes back unsymbolicated, or when asked what kind of crash something is.
debug-dumps
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
analyzing-memory-dumps-with-volatility
Analyzes RAM memory dumps from compromised systems using the Volatility framework to identify malicious processes, injected code, network connections, loaded modules, and extracted credentials. Supports Windows, Linux, and macOS memory forensics. Activates for requests involving memory forensics, RAM analysis, volatile data examination, process injection detection, or memory-resident malware investigation.