What problem does it solve?
Native VS Code crash dumps (.dmp) contain raw memory addresses and module names but no human-readable method names, making root-cause analysis nearly impossible without proper symbol files. This Skill walks through the full symbolication workflow so engineers can turn an opaque dump into an actionable backtrace.
Core Features & Use Cases
- Multi-source symbol resolution: Pulls symbols from public electron/electron releases for Code - OSS builds, and from the private microsoft/vscode-electron-prebuilt repo for Insiders/Stable builds.
- Cache-aware symbol matching: Copies .sym files into the electron-minidump breakpad cache using exact debug-id matching, with retry logic for transient download failures.
- Crash attribution guidance: Identifies the crashing module (VS Code, Electron, or third-party DLL) and process type (main, renderer, GPU, extension host) from dump strings.
- Use Case: A user reports VS Code crashing repeatedly on Windows. You grab the .dmp from the crash reporter directory, symbolicate it against the matching Insiders symbol zip, and discover the top frame is in a third-party antivirus DLL injected into the extension host process — confirming the crash is environmental, not a VS Code bug.
Quick Start
Symbolicate the crash dump at /tmp/crash.dmp and tell me which module and process caused the crash.