skills.rest
Tyrizx
TyrizxOFFICIAL
Explore all skills by this author →
GitHub

symbolicate-crash-dump

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

Updated Aug 30, 2026
Search Tags:#vscode#debugging#symbolication#backtrace#crash dump#breakpad#electron-minidump
One-click install
npx skills add https://github.com/Tyrizx/Tyrizx --skill symbolicate-crash-dump-tyrizx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: symbolicate-crash-dump
Source: https://github.com/Tyrizx/Tyrizx/tree/main/.github/skills/symbolicate-crash-dump
Command: npx skills add https://github.com/Tyrizx/Tyrizx --skill symbolicate-crash-dump-tyrizx

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 those dumps into symbolicated backtraces with method names, and attributing crashes to the correct module and process. ## Core Features & Use Cases - Crash Dump Symbolication: Run electron-minidump against a .dmp file, download matching Breakpad symbol files, and place them in the cache keyed by exact debug-id. - Symbol Acquisition Guidance: Download Insiders/Stable symbols from the private microsoft/vscode-electron-prebuilt releases via an authenticated GitHub CLI, or OSS Electron symbols from public electron/electron releases. - Crash Attribution: Identify the crashing module (VS Code/Electron vs third-party DLL) and process type (main, renderer, GPU, or extension host via node.mojom.NodeService) from the dump contents. - Use Case: A user reports an extension host crash-loop on Windows Stable. You obtain the .dmp file, run electron-minidump, fetch the matching stable-symbols zip for the right Electron version, copy the .sym files into the cache, and confirm the crash originates in a third-party antivirus DLL rather than VS Code. ## 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 produce a backtrace. Download the matching symbol zip for the crashed build's Electron version, copy the .sym files into the breakpad_symbols cache keyed by exact debug-id, and re-run symbolication.

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

Insiders and Stable symbols come from the private microsoft/vscode-electron-prebuilt releases, downloaded with an authenticated GitHub CLI using gh release download. Code - OSS symbols are publicly available from electron/electron releases. Releases are tagged by Electron version, not VS Code version.

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 fetch the matching platform symbol zip.

Why are method names still missing after adding symbols?▼

Breakpad matches symbols by exact debug-id, not version name, so the .sym file hash must exactly match what the cache directory expects. Some modules like runtime.node and third-party DLLs have no public symbols at all, so those frames cannot be symbolicated.

How do I identify which process crashed from a dump file?▼

Run strings on the dump and grep for markers like --type=renderer, --type=gpu-process, or node.mojom.NodeService. The extension host runs as a Node utility process, so node.mojom.NodeService indicates an extension host crash, while no --type marker means the main process.

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

Remote server extension host 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 -se <node-binary> -c <core-file> and collect bt full, info sharedlibrary, and registers.

Related Skills

Explore More Software Engineering Skills→
awfixers-stuffawfixers-stuff

core-dumps

Analyze Linux/macOS core dumps with GDB/LLDB and coredumpctl.

Official
Advanced
openharmonyinsightopenharmonyinsight
31

ohos-issue-graphics-cppcrash-analysis

Analyze OpenHarmony cppcrash logs to locate native graphics crash root causes.

Official
Advanced
riparinoriparino
1

defensive-crash-analysis

Analyze Windows crash telemetry to determine exploitability and identify exploitation patterns.

Community
Intermediate
jimehjimeh

symbolicate-crash-dump

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

Community
Advanced