CrashRpt

This article is a stub. You can help the wiki by expanding it.

See Towards better troubleshooting for the main article about this subject.

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... — chris (Nov 19th, 2015). Re: [Flightgear-devel] Some thoughts about the release process. (powered by Instant-Cquotes)

people have been working on features to provide backtraces to developers without end-users having to be aware of the whole process, as in the whole crashrpt thing that Zakalawe implemented - but all this is still in its infancy unfortunately. Just keep in mind that FlightGear users are not dealing with a finished or "polished" product - things are very much in flux, and people can be part of the evolutionary process here. — Hooray (Apr 22nd, 2014). Re: Forum communication. (powered by Instant-Cquotes)

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) — James Turner (Jan 23rd, 2014). [Flightgear-devel] Release candidates. (powered by Instant-Cquotes)

There is one other Windows area I could really use some help with - I added CrashRpt integration several releases ago and have a web server full of crash data. To make this useful someone with Windows skills needs to write some tooling to automaticly match a crash report to the archived PDB file and hence produce a usable back-trace. We could then start analysing the most common sources of crashes. If that’s something you have any interest in, I can explain in more detail. — James Turner (2015-03-23). Re: [Flightgear-devel] SimGear/FlightGear Portability Patches. (powered by Instant-Cquotes)

someone who knows Windows (and has some time available) needs to actually glue everything together using those tools and scripts. Ideally in a way we can run on the Jenkins slave or similar as an hourly job. That’s the current piece of the flow I never found time to work on myself, yet. — James Turner (Mar 23rd, 2015). Re: [Flightgear-devel] SimGear/FlightGear Portability Patches. (powered by Instant-Cquotes)

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. — James Turner (Jul 18th, 2014). Re: [Flightgear-devel] Win 64bit nightly is broken. (powered by Instant-Cquotes)

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) — James Turner (Jan 26th, 2014). Re: [Flightgear-devel] Some feedback. (powered by Instant-Cquotes)