integrate a win32 crash report tool

[Antoine Martin]

On Linux, we can more easily get gdb backtraces, even from users - see ​debugging with gdb.
But on win32, by the time we get a user report about a crash, all we are likely to hear is "it crashed, dr watson came up".

We ought to be able to do better than that. Maybe using:

• ​crashrpt
• ​breakpad

For a start, we can collect more data. The log file basic would be a start.

[Antoine Martin]

too late for 0.11

[Antoine Martin]

I think that the win32 client has been very stable, which means this is a less of a priority.

[Antoine Martin]

shows the alert box for a command line parsing error on the "quality" option

[Antoine Martin]

shows an alert box with some help text for a "help" command line option

[Antoine Martin]

As of r7100, we now have a catch-all alert box shown on win32 when the client exits because of an error. (this can be disabled by setting XPRA_MESSAGEBOX=0)

This does not apply to things like network disconnections which still use a non-zero exit code, this is only for bugs or other serious and unexpected problems.

Some examples:

[Antoine Martin]

I haven't seen any hard crashes (the useless dr watson) for a very long time.
So I don't think we need a crash handler.

What we could do however is:

• fire the bug report tool when we return to the launcher with an error
• allow the launcher to inject a buffer into the logging so that we can capture the client output and include it in bug reports
• maybe even always intercept error and warn level logging for bug reports?
• add the ability to more easily turn debugging on for certain things from the launcher

[Antoine Martin]

related: #752

[Antoine Martin]

Now that we have remote logging (see #786), I think this is good enough. (bar #637)

[Antoine Martin]

(update to correct milestone)