20,741
edits
CrashRpt: Difference between revisions
Jump to navigation
Jump to search
→Crash Report Analysis
| Line 62: | Line 62: | ||
# get them from James' server and process them manually (e.g. via the script I mentioned in my previous e-mail, altered as necessary): pros: no changes in existing libraries/infrastructure, dumps remain private and accessible only to trusted developers; cons: Windows-only, some manual steps and script editing are needed; | # get them from James' server and process them manually (e.g. via the script I mentioned in my previous e-mail, altered as necessary): pros: no changes in existing libraries/infrastructure, dumps remain private and accessible only to trusted developers; cons: Windows-only, some manual steps and script editing are needed; | ||
# use an automated solution like Dr Dump [1], which can be configured to accept CrashRpt reports; pros: only a small code change is needed, the service automatically analyes crash reports and groups them according to their stack traces (it is only needed to upload .pdb symbols); cons: Windows-only, possible privacy concerns (dumps might contain portions of memory storing personal data, and some people might not be comfortable with storing them on a third-party service); | # use an automated solution like Dr Dump [1], which can be configured to accept CrashRpt reports; pros: only a small code change is needed, the service automatically analyes crash reports and groups them according to their stack traces (it is only needed to upload .pdb symbols); cons: Windows-only, possible privacy concerns (dumps might contain portions of memory storing personal data, and some people might not be comfortable with storing them on a third-party service); | ||
# change the crash reporter to Google Breakpad [2]/Crashpad [3] and use an already developed frontend, like Socorro [4] or the Mini Breakpad Server [5], or some custom scripting; pros: cross-platform bug reports; cons: integrating Breakpad is not trivial (as well as huge [6]); Socorro is heavyweight (at least in my opinion). | # change the crash reporter to Google Breakpad [2]/Crashpad [3] and use an already developed frontend, like Socorro [4] or the Mini Breakpad Server [5], or some custom scripting; pros: cross-platform bug reports; cons: integrating Breakpad is not trivial (as well as huge [6]); Socorro is heavyweight (at least in my opinion). | ||
* [1] https://drdump.com/ | |||
* [2] https://chromium.googlesource.com/breakpad/breakpad/ | |||
* [3] https://crashpad.chromium.org/index.html | |||
* [4] https://wiki.mozilla.org/Socorro | |||
* [5] https://github.com/electron/mini-breakpad-server | |||
* [6] http://sourceforge.net/p/flightgear/mailman/message/31877484/<ref>{{cite web | |||
|url = http://sourceforge.net/p/flightgear/mailman/message/35062598/ | |url = http://sourceforge.net/p/flightgear/mailman/message/35062598/ | ||
|title = <nowiki>Re: [Flightgear-devel] Info on windows CrashRpts...</nowiki> | |title = <nowiki>Re: [Flightgear-devel] Info on windows CrashRpts...</nowiki> | ||