Jump to content
Setting up an AI agent? ReverseEngineering.wiki skill (works from the command line, no configuration): https://reverseengineering.wiki/skill/rewiki/SKILL.md · setup for every client, including MCP: https://reverseengineering.wiki/llms.txt · REWiki:Connect

Technique:Identifying crash reporting SDKs

From ReverseEngineering.wiki
Technique
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/ or sentry.dll / libsentry.so means Library:Sentry Native; crashreporter(.exe) plus .extra files and dumps is typical of Library:Breakpad (Mozilla style).
  • Strings: google_breakpad, crashpad::, sentry.native, CPad / section CPADinfo (Crashpad info), upload host names of BugSplat and Backtrace (Unverified, not read).
  • Dumps: .dmp starting with MDMP are Format:Minidump files; the ModuleList stream gives each module's CodeView record (RSDS GUID, age, PDB name) or ELF build id.

Getting names

  1. Read the module's debug id (PE: GUID + age from the CodeView record; ELF: build id with the first three fields byte-swapped).
  2. Ask a public symbol server for <name>/<id>/<name>.sym (Mozilla serves such files; most vendors do not).
  3. 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).