Breakpad: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(initial page)
 
(update this insanely old page)
 
(55 intermediate revisions by 16 users not shown)
Line 1: Line 1:
Just a braindump on what we'll need to replace Talkback with [http://code.google.com/p/airbag/ Airbag].
= Breakpad Integration into Mozilla =


# Client-side exception handler - win32 work happening in [https://bugzilla.mozilla.org/show_bug.cgi?id=354980 bug 354980].
Breakpad is a set of libraries for client-side crash reporting.  This page talks about integrating breakpad with Mozilla products. [http://groups.google.com/group/google-breakpad-discuss/browse_thread/thread/4f40867980fe7452 Breakpad was formerly called airbag]. The libraries are being developed as a [http://groups.google.com/group/google-breakpad-discuss/browse_thread/thread/2a082e9c8636031c narrowly scoped] Google code project. The breakpad libraries do not provide any crash-reporting UI, nor do they provide a server.
# Client-side minidump sender - win32 work happening in [https://bugzilla.mozilla.org/show_bug.cgi?id=354980 bug 354980].
 
# Server-side minidump collector, CGI to accept POSTed minidump data and store it somewhere - I have a seriously minimal one running that just sticks the minidumps in a SQLite db
Our implementation has multiple parts:
# Server-side minidump processor - Should be implemented by [http://airbag.googlecode.com/svn/trunk/src/processor/ airbag processor]
* crash reporter: Client integration to handle crash reporting so a central server can aggregate crash data to help improve our products.
# Build-time symbol collector - Probably provided by [http://airbag.googlecode.com/svn/trunk/src/tools/windows/dump_syms/ airbag tools]
* crash ingestion pipeline:
# Server-side symbol store - For matching up stackdumps with symbols, not sure how this will interact with other components.  Somewhat under-specified currently.
** collector (Antenna) that collects incoming crash reports
# Server-side webapp to show details of crash reports, like talkback-public currently, will need a database backend
** processor (Socorro) that processes crash reports including walking the stack in the minidump and symbolicating it
* crash analysis tools
** Crash Stats webapp (Socorro) for searching, viewing, and investigating crash reports
** myriad of other tools based that use the Crash Stats API and Telemetry tools
 
More information, source code, and mailing lists for breakpad library development can be found at the
[http://code.google.com/p/google-breakpad/ Breakpad Project Site].
 
See [[Socorro]] for more information on Crash Stats, the crash ingestion pipeline, and Socorro.
 
 
= Integration Team =
 
Contact the team on #breakpad channel on Matrix.

Latest revision as of 17:43, 17 April 2020

Breakpad Integration into Mozilla

Breakpad is a set of libraries for client-side crash reporting. This page talks about integrating breakpad with Mozilla products. Breakpad was formerly called airbag. The libraries are being developed as a narrowly scoped Google code project. The breakpad libraries do not provide any crash-reporting UI, nor do they provide a server.

Our implementation has multiple parts:

  • crash reporter: Client integration to handle crash reporting so a central server can aggregate crash data to help improve our products.
  • crash ingestion pipeline:
    • collector (Antenna) that collects incoming crash reports
    • processor (Socorro) that processes crash reports including walking the stack in the minidump and symbolicating it
  • crash analysis tools
    • Crash Stats webapp (Socorro) for searching, viewing, and investigating crash reports
    • myriad of other tools based that use the Crash Stats API and Telemetry tools

More information, source code, and mailing lists for breakpad library development can be found at the Breakpad Project Site.

See Socorro for more information on Crash Stats, the crash ingestion pipeline, and Socorro.


Integration Team

Contact the team on #breakpad channel on Matrix.