Breakpad: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(initial page)
 
No edit summary
Line 4: Line 4:
# 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 happening in [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 - I have a seriously minimal one running that just sticks the minidumps in a SQLite db
# Server-side minidump collector, CGI to accept POSTed minidump data and store it somewhere - I have a seriously minimal one running that just sticks the minidumps in a SQLite db
# Server-side minidump processor - Should be implemented by [http://airbag.googlecode.com/svn/trunk/src/processor/ airbag processor]
# Server-side minidump processor - Should be implemented by [http://airbag.googlecode.com/svn/trunk/src/processor/ airbag processor] (This could be coupled with the minidump collector)
# Build-time symbol collector - Probably provided by [http://airbag.googlecode.com/svn/trunk/src/tools/windows/dump_syms/ airbag tools]
# Build-time symbol collector - Probably provided by [http://airbag.googlecode.com/svn/trunk/src/tools/windows/dump_syms/ airbag tools]
# Server-side symbol store - For matching up stackdumps with symbols, not sure how this will interact with other componentsSomewhat under-specified currently.
# Server-side symbol store - For matching up stackdumps with symbols.  Probably on y a file-based system will be implemented in Airbag, we may need a database-backed system.
# 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.

Revision as of 17:10, 3 October 2006

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

  1. Client-side exception handler - win32 work happening in bug 354980.
  2. Client-side minidump sender - win32 work happening in bug 354980.
  3. Server-side minidump collector, CGI to accept POSTed minidump data and store it somewhere - I have a seriously minimal one running that just sticks the minidumps in a SQLite db
  4. Server-side minidump processor - Should be implemented by airbag processor (This could be coupled with the minidump collector)
  5. Build-time symbol collector - Probably provided by airbag tools
  6. Server-side symbol store - For matching up stackdumps with symbols. Probably on y a file-based system will be implemented in Airbag, we may need a database-backed system.
  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.