Confirm
321
edits
Changes
no edit summary
# 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.
# [[Airbag/Symbol Server|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
Some of the Seneca students are [http://zenit.senecac.on.ca/wiki/index.php/Airbag_development_and_server_operation looking into this].
