What problem does it solve? Native VS Code crash dumps (.dmp files) contain raw memory addresses instead of readable method names, making root-cause analysis nearly impossible. This Skill walks you through turning a minidump into a symbolicated backtrace so you can identify which module and process crashed. ## Core Features & Use Cases - Symbolication Workflow: Runs electron-minidump, identifies missing symbols, downloads matching symbol files from microsoft/vscode-electron-prebuilt or electron/electron releases, and copies them into the breakpad cache by exact debug-id. - Crash Attribution: Identifies the crashing module (first-party vs third-party injected DLL) and process type (main, renderer, GPU, or extension host via node.mojom.NodeService markers). - Remote Crash Analysis: Covers Linux remote extension host crashes using core dumps and gdb instead of electron-minidump. - Use Case: A user reports an extension host crash-loop on Windows. You obtain the .dmp file, symbolicate it against the Stable Electron 42.5.0 symbols, and discover the top frame belongs to a third-party antivirus DLL injected into the NodeService utility process. ## Quick Start Symbolicate the attached crash dump file and tell me which module and process caused the crash.