20,741
edits
CrashRpt: Difference between revisions
Jump to navigation
Jump to search
m
needs de-quoting
No edit summary |
m (needs de-quoting) |
||
| Line 1: | Line 1: | ||
{{Stub}} | {{Stub}} | ||
{{Main article|Towards better troubleshooting}} | {{Main article|Towards better troubleshooting}} | ||
{{FGCquote | |||
|1= the Windows builds (and the 3.0 release, assuming no issues are encountered) now includes a crash-reporting framework. If you experience a crash, please send a report using the dialog which appears - you can provide some additional info if you wish. Your log file, some system info (processor, time of day, Windows version, path to fgfs.exe) and a crash dump areipped-up and sent to a server, and using some additional steps a real back-trace can be produced. (We need to write a privacy policy document for this, current the URL is a 404 - basically saying we promise not to do anything evil with the report info, although I’m not sure how much evil is possible since it’s the same info we ask for in a bug-report - I have switched off the options to include registry contents, and FGFS doesn’t touch the registry anyway) (For the curious, I’m not using Google Breakpad because it’s huge and seems somewhat inactive, instead I’m using CrashRpt which is very compact, completely open-source and new-BSD-licensed: https://code.google.com/p/crashrpt/ - although we do need to include a copy of their license.txt file somewhere in the installer) | |||
|2= {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/31877484/ | |||
| title = <nowiki>[Flightgear-devel] Release candidates</nowiki> | |||
| author = <nowiki>James Turner</nowiki> | |||
| date = Jan 23rd, 2014 | |||
}} | |||
}} | |||
{{FGCquote | {{FGCquote | ||
| Line 11: | Line 21: | ||
}} | }} | ||
{{FGCquote | |||
|1= Originally I only enabled CrashRpt for release builds, not nightlies, but I think it has been enabled since then. Also I explicity *disabled* the video capture support, because I felt the overhead of it would be too invasive when running FG, and the amount of video you’d need to record to make any difference to most crashes would be large. | |||
|2= {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/32621598/ | |||
| title = <nowiki>Re: [Flightgear-devel] Win 64bit nightly is broken</nowiki> | |||
| author = <nowiki>James Turner</nowiki> | |||
| date = Jul 18th, 2014 | |||
}} | |||
}} | |||
{{FGCquote | |||
|1= CrashRpt was something I wanted to get on the release branch - I am not sure whether to disable it for non-release branches entirely, or support it in the Windows nightly builds, where it would potentially be useful. (In which case there are further change to be done, since the nightlies use a different installer script) | |||
|2= {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/31886770/ | |||
| title = <nowiki>Re: [Flightgear-devel] Some feedback</nowiki> | |||
| author = <nowiki>James Turner</nowiki> | |||
| date = Jan 26th, 2014 | |||
}} | |||
}} | |||
<references/> | |||
[[Category:Core developer documentation]] | [[Category:Core developer documentation]] | ||