20,741
edits
CrashRpt: Difference between revisions
Jump to navigation
Jump to search
no edit summary
m (spelling) |
No edit summary |
||
| Line 1: | Line 1: | ||
{{Stub}} | {{Stub}} | ||
{{Main article|Towards better troubleshooting}} | {{Main article|Towards better troubleshooting}} | ||
{{Note|James' crash report system, is still in a preliminary state. Anyway, until this system is improved, the {{Ticket}} system (url!) is the way to communicate bugs to the developers.<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=293932#p293932 | |||
|title = <nowiki> Re: What has happened to FlightGear? </nowiki> | |||
|author = <nowiki> bugman </nowiki> | |||
|date = Sep 7th, 2016 | |||
|added = Sep 7th, 2016 | |||
|script_version = 0.40 | |||
}}</ref> | |||
}} | |||
the Windows builds (and the 3.0 release, assuming no issues are encountered) now includes a crash-reporting framework, to help getting higher quality crash reports <ref> {{cite web | the Windows builds (and the 3.0 release, assuming no issues are encountered) now includes a crash-reporting framework, to help getting higher quality crash reports <ref> {{cite web | ||
| Line 9: | Line 20: | ||
}} | }} | ||
</ref> | </ref> | ||
}} | |||
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 are zipped and sent to a server. Using some additional steps a real back-trace can be produced. (We need to write a privacy policy document for this - currently 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) <ref> {{cite web | 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 are zipped and sent to a server. Using some additional steps a real back-trace can be produced. (We need to write a privacy policy document for this - currently 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) <ref> {{cite web | ||