|Note Should look at CrashPad instead|
the author of CrashRpt has open sourced CrashFix, the report processing component , so there is no more need for a separate script (the batch import function of that application can be used to get existing reports into it, as long as reports themselves are divided according to the FG version they refer to).  http://crashfix.sourceforge.net/ 
archiving PDBs only work for an official (Jenkins) build since it needs to match exactly, but if you compiled FG yourself, presumably you can compile a debug version. There’s existing tooling (dbghelp.dll, which I assume the CrashFix tool uses) to combine a MiniDump with PDB files. It does require PDB files from Simgear, FlightGear and ideally OSG, but since we compile all the components, adding the MSVC flags to generate the PDBs, and have Jenkins archive them, is not a huge problem. The only question is which builds we maintain the archive for, since it will add some storage overhead somewhere. In my ideal world we’d have the processing script / tools runs /on the crash uploader server/, but since it’s a DreamHost virtual host, that is tricky. I’m more than happy to adjust the scripts to send theips to ‘someone else’ who can also receive the PDBs from Jenkins and then run the processing tool daily or whenever new reports arrive.
- Alessandro Menti (May 5th, 2016). Re: [Flightgear-devel] Info on windows CrashRpts....
- James Turner (May 6th, 2016). Re: [Flightgear-devel] Info on windows CrashRpts....