Skip to content
SPECIFICTION
Get listed

Breakpad

chromium.googlesource.com

Free plan WindowsmacOSLinuxAndroidSelf-hosted
Visit chromium.googlesource.com
Spec score 8.9 #7 of 26 in Game Crash Reporting Software

What it is

Breakpad is a free library and tool suite for capturing application crashes in compact minidump files and converting them into readable C and C++ stack traces. Its client can write a dump when a crash happens or when an application requests one. A symbol dumper converts compiler debugging information, including DWARF, STABS, and Windows PDB files, into Breakpad symbol files; a processor combines those symbols with dumps to produce traces. The sender can transmit dumps and application-defined key-value parameters to a crash server in a multipart HTTP POST request, with HTTPS supported. Developers provide the server and keep symbol files where the processor can access them. Documentation describes integration on Windows, macOS, and Linux, with Android also listed among the platforms. Windows out-of-process dump generation needs a separately run crash generation server. On Linux, crash callbacks should do little because application state may be unsafe; the client design also cautions against heap use and resource allocation after an exception. The project is hosted in the Chromium source repository and lists separate discussion and development mailing lists. The free plan costs nothing.

Spec sheet

Purpose
Breakpad is a set of client and server components that implement a crash-reporting system.Read 4 Oct 2026 · chromium.googlesource.com
Build and install
The repository instructions build Breakpad with ./configure and make, and optionally install built libraries with make install.Read 4 Oct 2026 · chromium.googlesource.com
Components
Its three main components are a client library, a symbol dumper, and a processor that creates human-readable stack traces from minidumps and symbol files.Read 4 Oct 2026 · chromium.googlesource.com
Crash capture
Its client library records crashes in compact minidump files and can also write minidumps on request when a program has not crashed.Read 4 Oct 2026 · chromium.googlesource.com
Crash upload
The sender library transmits a minidump and application-defined key-value parameters to a crash server using a multipart HTTP POST request.Read 4 Oct 2026 · chromium.googlesource.com
Crash-time constraint
The client design cautions that code running after an exception should avoid heap use and resource allocation because application state may be unsafe.Read 4 Oct 2026 · chromium.googlesource.com
Current release tag
The repository lists v2024.02.16 among its tags.Read 4 Oct 2026 · chromium.googlesource.com
Linux build
The Linux guide says the Autotools build produces client and processor libraries, and describes linking the client library into an application.Read 4 Oct 2026 · chromium.googlesource.com
Linux callback constraint
The Linux guide says to do as little work as possible in the crash callback because the application may be in an unsafe state.Read 4 Oct 2026 · chromium.googlesource.com
Mac integration
The Mac guide describes adding Breakpad.framework to an Xcode project and using dump_syms to create symbol files during the build.Read 4 Oct 2026 · chromium.googlesource.com
Maker details
The pages opened identify Breakpad as a project hosted in the Chromium source repository and do not state a company headquarters or founding date.Read 4 Oct 2026 · chromium.googlesource.com
Minidump contents
A minidump can include loaded executable and library identities, thread register and stack data, and system details such as processor and operating system versions.Read 4 Oct 2026 · chromium.googlesource.com
On-demand dumps
The client can write a minidump when a crash occurs or when the application requests one.Read 4 Oct 2026 · chromium.googlesource.com
Out-of-process handling
Windows out-of-process dump generation requires a separately run crash generation server, whose process logistics are left to the integrator.Read 4 Oct 2026 · chromium.googlesource.com
Self-hosted processing
The processor uses symbol files that developers store where the minidump processor can find them; the documentation describes uploading symbols to a server developers have written.Read 4 Oct 2026 · chromium.googlesource.com
Support and community
The project lists a discussion mailing list for questions and a separate mailing list for development and reviews.Read 4 Oct 2026 · chromium.googlesource.com
Support channel
The repository lists a Google Breakpad discussion group for questions and a separate developer group for reviews.Read 4 Oct 2026 · chromium.googlesource.com
Supported operating systems
The project documentation describes client integration for Windows, macOS, and Linux.Read 4 Oct 2026 · chromium.googlesource.com
Supported systems
The getting-started documentation describes crash handling on Windows, OS X, and Linux.Read 4 Oct 2026 · chromium.googlesource.com
Symbol formats
The symbol dumper reads compiler debugging information including DWARF, STABS, and Windows PDB files and creates Breakpad symbol files.Read 4 Oct 2026 · chromium.googlesource.com
Symbol upload
The documentation describes symupload as a tool for sending symbol files to a server that accepts them, including via HTTP POST on macOS.Read 4 Oct 2026 · chromium.googlesource.com
Symbolicated traces
The processor uses symbol files to turn minidumps into human-readable C and C++ stack traces.Read 4 Oct 2026 · chromium.googlesource.com
Transport security
The sender supports HTTPS because crash dumps may contain sensitive data.Read 4 Oct 2026 · chromium.googlesource.com
Upload workflow
Breakpad provides upload-related code and tools, but its documentation expects the application team to send minidumps to a server for analysis.Read 4 Oct 2026 · chromium.googlesource.com
Windows integration
Windows applications integrate the exception handler library, and out-of-process dump generation uses a separately instantiated crash generation server.Read 4 Oct 2026 · chromium.googlesource.com

Plans and prices

Breakpad Free Open-source crash-reporting library and tool suite · self-built and self-hosted components Read 4 Oct 2026 · chromium.googlesource.com

Every Breakpad plan and price →

Strong points and limits

Strong points

  • Free plan costs nothing
  • Can create dumps on crashes or by request
  • Sender supports HTTPS
  • Processor produces readable C and C++ traces

Limits

  • Developers provide a server for analysis
  • Windows out-of-process dumps need a separate server
  • Crash callbacks must avoid substantial work

Who it suits

Breakpad suits developers who need crash capture and symbolicated C or C++ traces and can manage their own server and symbol files. It is aimed at teams integrating crash handling into Windows, macOS, or Linux applications.

Verdict

Breakpad supplies capture, symbol processing, and upload-related components, but the application team must operate the analysis workflow. Its crash-time constraints and platform-specific integration requirements are worth considering before adoption.

Where Specifiction places it

Alternatives to BreakpadAll alternatives →