What problem does it solve? Native VS Code crash dumps (.dmp files) contain raw memory addresses instead of method names, making it nearly impossible to identify which module or process caused a crash without the correct Breakpad symbol files. ## Core Features & Use Cases - Symbolication Workflow: Runs electron-minidump against a crash dump, identifies modules missing symbols, and guides downloading matching symbol zips from microsoft/vscode-electron-prebuilt or electron/electron releases. - Cache Management: Explains how to copy .sym files into the electron-minidump breakpad_symbols cache keyed by exact debug-id, with retry logic for transient symbol download failures. - Crash Attribution: Provides techniques to identify the crashing module (VS Code vs third-party DLL) and process type (main, renderer, GPU, or extension host via node.mojom.NodeService) using strings analysis. - Use Case: A VS Code team member receives a Stable Windows x64 crash dump, downloads the matching stable-symbols zip for the correct Electron version, copies hash-matched .sym files into the cache, and produces a backtrace showing the crash originated in an injected antivirus DLL. ## Quick Start Symbolicate the attached crash dump file and tell me which module and process caused the crash.