skills.rest
Niiihuel
NiiihuelCOMMUNITY
Explore all skills by this author →
GitHub

symbolicate-crash-dump

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

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

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 it nearly impossible to identify which module or process caused a crash without a structured symbolication workflow. ## Core Features & Use Cases - Crash Dump Symbolication: Runs electron-minidump against a .dmp file and resolves missing method names by fetching the correct Breakpad symbol files. - Symbol Acquisition Guidance: Walks through downloading matching symbol zips from microsoft/vscode-electron-prebuilt (Insiders/Stable) or electron/electron releases (Code - OSS), matched by Electron version, quality, platform, and architecture. - Root Cause Analysis: Identifies the crashing module and process type (main, renderer, GPU, or extension host via node.mojom.NodeService) to attribute crashes to VS Code, Electron, or third-party injected DLLs. - Use Case: A VS Code team member receives a user-reported extension host crash dump, symbolicates it, confirms the top frame is a third-party antivirus DLL injected into the NodeService utility process, and attributes the crash to that vendor's software. ## 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 symbolicated backtrace. If method names are missing, download the matching symbol zip for the build's Electron version and copy the .sym files into the electron-minidump breakpad_symbols cache, then re-run.

How do I get symbol files for VS Code Insiders or Stable crashes?▼

Insiders and Stable symbols live in the private microsoft/vscode-electron-prebuilt repo, so you need an authenticated GitHub CLI. Find the Electron version in the build's .npmrc, then use gh release download with the matching quality, platform, and architecture symbol zip.

Can I symbolicate crash dumps on Windows?▼

No, electron-minidump does not run on Windows; a macOS or Linux device is required. You can still symbolicate Windows-produced .dmp files, but the symbolication tooling itself must run on macOS or Linux.

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

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

How do I identify which process crashed in a VS Code dump?▼

Run strings on the dump and grep for --type markers or utility-sub-type values. node.mojom.NodeService indicates the extension host, --type=renderer a workbench window, --type=gpu-process the GPU process, and no 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 in gdb against the server's node binary and capture bt full, registers, and shared library info.

Related Skills

Explore More Software Engineering Skills→
TyrizxTyrizx

symbolicate-crash-dump

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

Official
Advanced
jimehjimeh

symbolicate-crash-dump

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

Community
Advanced
NexVarNexVar
3

Huly CLI Skill

Access Huly workspace operations via CLI with structured JSON output.

Official
Intermediate
RosyGameStudioRosyGameStudio

point-light-shadows

Implement omnidirectional point light shadows with cube map depth textures in SDL GPU projects.

Official
Advanced