Implement support for saving crash reports

[anevilyak]

In order for the Debugger to replace gdb, it needs the ability to save problem reports for crashed apps. These should at the very least include stack traces for all running threads, as well as possibly the register states if available, and also possibly the list of loaded libraries.

[anevilyak]

I'm a bit torn on the best way to proceed for this one. What I originally had in mind was as follows:

• debug_server's crash dialog would gain a "Save Crash Report" button. The latter would auto-generate a crash report file name based off the name/id of the crashed team + timestamp.

• Said filename would get passed to Debugger along with an option telling it to simply save a crash report and exit.

On the debugger side however, start_team_debugger() currently requires a user interface object to be passed to it. Since in this instance I don't ever want to present the user with a UI, there seem to be two possible ways to go here. Either 1) create a third UserInterface derivative which simply no-ops the various UI calls, and implements Show() to retrieve the appropriate information, write it to disk, and terminate, or 2) Add the functionality in question to the command line interface together with a flag telling it to not enter its UI loop but rather call the crash report functionality instead. Any preference, or perhaps a different approach entirely?

[bonefish]

If you can hold the horses for a bit longer, I'd first like to add a bit more stuff to the CLI. Since what is put into the crash report will possibly be very similar to what the stack trace command and others print, I think it makes sense to finish those first and then see how to best use or refactor the functionality for the crash report. I actually intended to look into that afterward myself, but if you want you can do that, of course.

[anevilyak]

That's fine by me, I have plenty of other tickets to work on :)

[anevilyak]

While there are still some details remaining to be fleshed out in the case where no debug information is available, this feature is now implemented.