Breakpad: Difference between revisions

759 bytes removed ,  17 April 2020
update this insanely old page
(update this insanely old page)
 
(7 intermediate revisions by 4 users not shown)
Line 3: Line 3:
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.
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 three 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 server that collects and processes collected crash data and uses a symbol server to convert raw dumps into readable stack traces.  The processor can insert the resulting data into a database.
* crash ingestion pipeline:
* A web interface for viewing and parsing crash reports, called [http://code.google.com/p/socorro/ Socorro].
** 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
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].


= Pages =
See [[Socorro]] for more information on Crash Stats, the crash ingestion pipeline, and Socorro.
* [[Breakpad/Updating_to_latest_Breakpad_from_SVN|How to update the Breakpad snapshot in mozilla-central to the latest Breakpad code in SVN]]
 
* [[Breakpad/Design]] (Design and planning information)
* [[Breakpad/Status Meetings|Status Meetings]] (Agendas/Minutes)
* [[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/SkipList | SkipList]] -- How to file a SkipList bug


= Integration Team =
= Integration Team =


The following people are actively working on Breakpad integration:
Contact the team on #breakpad channel on Matrix.
 
* luser (client and build systems, minidump_stackwalk)
* lars (server, python, middleware)
* ozten (server, middleware, materialized views, front end)
* ryan snyder (webUI, front end, JS)
* chowse (UX)
* aravind (IT)
* jabba (IT)
* deinspanjer (hbase lead, hadoop admin)
* stephend, vish_moz, automatedtester (WebQA/automation)
* choffman
* laura (project)
 
Contact the team at socorro-dev@mozilla.com
Confirmed users
537

edits