20,741
edits
CrashRpt: Difference between revisions
Jump to navigation
Jump to search
m
updates from devel list - this may benefit from dequoting/cleanup sooner or later ...
No edit summary |
m (updates from devel list - this may benefit from dequoting/cleanup sooner or later ...) |
||
| Line 1: | Line 1: | ||
{{Stub}} | {{Stub}} | ||
{{Main article|Towards better troubleshooting}} | {{Main article|Towards better troubleshooting}} | ||
I've also done some research about automating crash analysis - there are the following solutions: 1) 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; 2) 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); 3) 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). Cheers, Alessandro Menti [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/ | |||
|title = <nowiki>Re: [Flightgear-devel] Info on windows CrashRpts...</nowiki> | |||
|author = <nowiki>Alessandro Menti</nowiki> | |||
|date = May 4th, 2016 | |||
|added = May 4th, 2016 | |||
|script_version = 0.28 | |||
}} | |||
</ref> | |||
MD5 errors are normal - the address I gave you is the one where the error reports are uploaded by CrashRpt itself (I should have specified that), and the crashrpt.php script requires several parameters to be passed, including an MD5 hash of the minidump (I think), hence the message. There is currently no public interface to get crash reports.<ref>{{cite web | |||
|url = http://sourceforge.net/p/flightgear/mailman/message/35062598/ | |||
|title = <nowiki>Re: [Flightgear-devel] Info on windows CrashRpts...</nowiki> | |||
|author = <nowiki>Alessandro Menti</nowiki> | |||
|date = May 4th, 2016 | |||
|added = May 4th, 2016 | |||
|script_version = 0.28 | |||
}} | |||
</ref> | |||
Right now, they are (unfortunately) archived there (see the end of [1]). You can help by writing a tool to match crash reports to PDB files; I've written a small script [2] which could help you get started. | |||
[1] http://article.gmane.org/gmane.games.flightgear.devel/77237 | |||
[2] http://article.gmane.org/gmane.games.flightgear.devel/77508<ref>{{cite web | |||
|url = http://sourceforge.net/p/flightgear/mailman/message/35061554/ | |||
|title = <nowiki>Re: [Flightgear-devel] Info on windows CrashRpts...</nowiki> | |||
|author = <nowiki>Alessandro Menti</nowiki> | |||
|date = May 3rd, 2016 | |||
|added = May 4th, 2016 | |||
|script_version = 0.28 | |||
}} | |||
</ref> | |||
{{FGCquote | {{FGCquote | ||
|1= Might sth like a bug-report (or maybe crash-report?) feature be of help? We got a lot of information in the property-tree, like GPU-drivers etc. For instance, do we have OS and stuff like that too? Might be fairly easy to put this important info into a tmp-file, and in the case we crash, add it to some kind of http-request to flightgear.org. An experience-report might be of help, what frequently asked questions do you pose all the time? + the red box... | |1= Might sth like a bug-report (or maybe crash-report?) feature be of help? We got a lot of information in the property-tree, like GPU-drivers etc. For instance, do we have OS and stuff like that too? Might be fairly easy to put this important info into a tmp-file, and in the case we crash, add it to some kind of http-request to flightgear.org. An experience-report might be of help, what frequently asked questions do you pose all the time? + the red box... | ||