Technique:Identifying crash reporting SDKs
Appearance
| On this wiki | Facts · Code · Notes · Topics |
|---|
How to tell which crash reporter a program embeds (Breakpad, Crashpad, Sentry, BugSplat, Backtrace) from files, strings and sections, and how to use its minidumps and symbol files to get function names.
Quick identification
- Files:
crashpad_handler(.exe)means Library:Crashpad;.sentry-native/orsentry.dll/libsentry.someans Library:Sentry Native;crashreporter(.exe)plus.extrafiles and dumps is typical of Library:Breakpad (Mozilla style). - Strings:
google_breakpad,crashpad::,sentry.native,CPad/ sectionCPADinfo(Crashpad info), upload host names of BugSplat and Backtrace (Unverified, not read). - Dumps:
.dmpstarting withMDMPare Format:Minidump files; the ModuleList stream gives each module's CodeView record (RSDS GUID, age, PDB name) or ELF build id.
Getting names
- Read the module's debug id (PE: GUID + age from the CodeView record; ELF: build id with the first three fields byte-swapped).
- Ask a public symbol server for
<name>/<id>/<name>.sym(Mozilla serves such files; most vendors do not). - Apply the FUNC/PUBLIC lines at image base + RVA. Details in Format:Breakpad symbol file.
If a PDB exists instead, see Format:PDB (Program Database).