symbolicate-crash-dump

Symbolicate native VS Code crash dumps into readable backtraces using electron-minidump.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/basedgod55hjl/vsbrax --skill symbolicate-crash-dump-basedgod55hjl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: symbolicate-crash-dump
Source: https://github.com/basedgod55hjl/vsbrax/tree/main/.github/skills/symbolicate-crash-dump
Command: npx skills add https://github.com/basedgod55hjl/vsbrax --skill symbolicate-crash-dump-basedgod55hjl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires electron-minidump.

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.

Frequently Asked Questions about symbolicate-crash-dump

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

FAQPage Schema
How do I symbolicate a VS Code crash dump file?▼

Install electron-minidump globally with npm, then run electron-minidump crash-file.dmp to generate a backtrace. Download matching symbol files for the Electron version, copy them into the breakpad_symbols cache by exact debug-id, and re-run symbolication.

Where do I download Electron symbol files for VS Code crashes?▼

Insiders and Stable builds use symbols from the private microsoft/vscode-electron-prebuilt releases, downloaded with an authenticated GitHub CLI. OSS builds use public symbols from electron/electron releases, matched by Electron version, platform, and architecture.

Can I symbolicate a crash dump on Windows?▼

No, electron-minidump does not run on Windows; you need a macOS or Linux device to symbolicate. The crash dump itself can come from any platform, including Windows, as long as you process it on a supported host.

Why are method names still missing after adding symbol files?▼

Breakpad matches symbols by exact debug-id, not version name, so a same-version zip from a different build pipeline will not be used. Verify the .sym file hash matches the cache directory, and note that runtime.node and third-party modules often have no public symbols at all.

How do I identify which process crashed from a minidump?▼

Search the dump strings for markers like --type=renderer, --type=gpu-process, or utility-sub-type=node.mojom.NodeService. The NodeService utility process corresponds to the extension host, while no --type marker indicates the main process.

How do I analyze a remote extension host crash on Linux?▼

Remote server crashes use core dumps and gdb instead of electron-minidump. Enable core dumps with ulimit -c unlimited, retrieve the core via coredumpctl, then load it with gdb against the server's node binary and capture backtrace and register output.