Breakpad: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
(updated info)
Line 1: Line 1:
Just a braindump on what we'll need to replace Talkback with [http://code.google.com/p/airbag/ Airbag].
Just a braindump on what we'll need to replace Talkback with [http://code.google.com/p/airbag/ Airbag].


# Client-side exception handler - win32 work happening in [https://bugzilla.mozilla.org/show_bug.cgi?id=354980 bug 354980].
# Client-side exception handler - win32 work done ([https://bugzilla.mozilla.org/show_bug.cgi?id=354980 bug 354980]).
# Client-side minidump sender - win32 work happening in [https://bugzilla.mozilla.org/show_bug.cgi?id=354980 bug 354980].
# Client-side minidump sender - win32 work done ([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, or just call the processor directly. [http://mavra.perilith.com/~luser/airbag-collector/index.txt My simplistic collector]
# Server-side minidump collector, CGI to accept POSTed minidump data.  Current plans are just to call the minidump processor directly from this CGI. [http://mavra.perilith.com/~luser/airbag-collector/index.txt My simplistic collector].  [https://bugzilla.mozilla.org/show_bug.cgi?id=358302 bug 358302] covers setting up an official server.
# Server-side minidump processor - Mostly implemented by [http://airbag.googlecode.com/svn/trunk/src/processor/ airbag processor], in the minidump_stackwalk example program.  We will need to implement a SymbolSupplier that can match up modules with their symbols (This could be coupled with the minidump collector)
# Server-side minidump processor - Mostly implemented by [http://airbag.googlecode.com/svn/trunk/src/processor/ airbag processor], in the minidump_stackwalk example program, we will probably want to modify that a bit to make the output more machine readable, so we can store it in a DB.
# Build-time symbol extractor - Probably provided by [http://airbag.googlecode.com/svn/trunk/src/tools/windows/dump_syms/ airbag tools]
# Build-time symbol extractor - Provided by [http://airbag.googlecode.com/svn/trunk/src/tools/windows/dump_syms/ airbag tools], [https://bugzilla.mozilla.org/show_bug.cgi?id=359151 bug 359151] is to get it hooked up in the build system.
# Server-side symbol store - For matching up stackdumps with symbols.  This probably just needs to be an organized filesystem, ala, Microsoft's Symbol Server.  The symbol files extracted from firefox.pdb on Windows appear to be in the 30-60Mb range, but since they're text they compress very well.
# Server-side symbol store - For matching up stackdumps with symbols.  This will just be an organized filesystem setup like Microsoft's Symbol Server.  The symbol files extracted from firefox.pdb on Windows appear to be in the 30-60Mb range, but since they're text they compress very well.  The [http://airbag.googlecode.com/svn/trunk/src/processor/simple_symbol_supplier.cc simple symbol supplier] from airbag uses this, and should be sufficient.
# Server-side webapp to show details of crash reports, like talkback-public currently, will need a database backend
# Server-side webapp to show details of crash reports, like talkback-public currently, will need a database backend


[http://groups.google.com/group/airbag-discuss/browse_thread/thread/2a082e9c8636031c Mento's post] outlines the Airbag project's proposed scope.
[http://groups.google.com/group/airbag-discuss/browse_thread/thread/2a082e9c8636031c Mento's post] outlines the Airbag project's proposed scope.

Revision as of 09:08, 2 November 2006

Just a braindump on what we'll need to replace Talkback with Airbag.

  1. Client-side exception handler - win32 work done (bug 354980).
  2. Client-side minidump sender - win32 work done (bug 354980).
  3. Server-side minidump collector, CGI to accept POSTed minidump data. Current plans are just to call the minidump processor directly from this CGI. My simplistic collector. bug 358302 covers setting up an official server.
  4. Server-side minidump processor - Mostly implemented by airbag processor, in the minidump_stackwalk example program, we will probably want to modify that a bit to make the output more machine readable, so we can store it in a DB.
  5. Build-time symbol extractor - Provided by airbag tools, bug 359151 is to get it hooked up in the build system.
  6. Server-side symbol store - For matching up stackdumps with symbols. This will just be an organized filesystem setup like Microsoft's Symbol Server. The symbol files extracted from firefox.pdb on Windows appear to be in the 30-60Mb range, but since they're text they compress very well. The simple symbol supplier from airbag uses this, and should be sufficient.
  7. Server-side webapp to show details of crash reports, like talkback-public currently, will need a database backend

Mento's post outlines the Airbag project's proposed scope.