Breakpad: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(lots of cleanup)
(update this insanely old page)
 
(29 intermediate revisions by 14 users not shown)
Line 1: Line 1:
= What's Breakpad? =
= Breakpad Integration into Mozilla =
Breakpad is a crash reporting tool.  This page talks about its implementation for Mozilla.


[http://groups.google.com/group/google-breakpad-discuss/browse_thread/thread/4f40867980fe7452 Breakpad used to be Airbag]. I'm cleaning up this page, so hopefully it will suck less!
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.


Our implementation has two parts:
Our implementation has multiple parts:
* Client integration to handle crash reporting so a central server can aggregate crash data to help improve our products.
* crash reporter: Client integration to handle crash reporting so a central server can aggregate crash data to help improve our products.
* A web interface for viewing and parsing Airbag reports--We call it [http://code.google.com/p/socorro/ Socorro].
* 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 about Breakpad itself can be found at:
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]
[http://code.google.com/p/google-breakpad/ Breakpad Project Site].
* [http://google-breakpad.googlecode.com/svn/ Breakpad Source]
* [http://groups.google.com/group/google-breakpad-discuss Breakpad Discussion Newsgroup]
* [http://groups.google.com/group/google-breakpad-dev Breakpad Dev Newsgroup]


= Pages =
See [[Socorro]] for more information on Crash Stats, the crash ingestion pipeline, and Socorro.
* [[Breakpad:Current_Implementation|Current Implementation]] -- The status of what has been implemented so far.
* [[Breakpad:Feature_List|Feature List]] -- What do we want our Breakpad web interface to do?
* [[Breakpad:Server_Requirements|Server Requirements]] -- How to set up the web app.
** [[Breakpad:Development Planning & Design | Development Planning & Design]]
* [[Breakpad/Symbol_Server|Breakpad Symbol Server]]
* [http://zenit.senecac.on.ca/wiki/index.php/Airbag_development_and_server_operation Seneca College Airbag Page] -- Read about Seneca's awesome work with Airbag.


Win32 trunk nightlies currently include the airbag code, but it's disabled at runtime by default.  To test it, you will need to set the environment variable <code>MOZ_AIRBAG=1</code>.  Crash reports are currently collected at:
http://mavra.perilith.com/~luser/airbag-collector/list.py


http://benjamin.smedbergs.us/blog/2006-09-12/deploying-the-airbag/
= 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.