Yet I, a mere user, can look at my Full Crash Dumps, run them through the MS WinDbg, and see exactly the line of disassembled code, that is causing the CTD (typically a VERY OBVIOUS Null Pointer, returning Zero or -1), but without the symbol table / source or interfaced to VS, it is difficult to tell where in MSFS this bit of code is running.
As a user, also NOT what I should be expected to be doing 