Breakpad: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 6: Line 6:
# 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.
# 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 - 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.
# 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 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.
# [[Airbag/Symbol Server|Server-side symbol store]] - For matching up stackdumps with symbols.
# 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


Line 15: Line 15:


Some of the Seneca students are [http://zenit.senecac.on.ca/wiki/index.php/Airbag_development_and_server_operation looking into this].
Some of the Seneca students are [http://zenit.senecac.on.ca/wiki/index.php/Airbag_development_and_server_operation looking into this].
We can get Windows symbols here: [http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx Download Windows Symbol Packages] and run dump_syms on them to make them useful to airbag.

Revision as of 20:28, 17 November 2006

Just a braindump on what we'll need to replace Talkback with Airbag. There's a tracking bug on this now, bug 360327.

  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.
  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.

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 MOZ_AIRBAG=1. Crash reports are currently collected at: http://mavra.perilith.com/~luser/airbag-collector/list.pl

Some of the Seneca students are looking into this.

Retrieved from "https://wiki.allizom.org/index.php?title=Breakpad&oldid=42270"