#392 closed enhancement (fixed)
integrate a win32 crash report tool
Reported by: | Antoine Martin | Owned by: | Antoine Martin |
---|---|---|---|
Priority: | major | Milestone: | 0.14 |
Component: | client | Version: | |
Keywords: | Cc: |
Description
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:
For a start, we can collect more data. The log file basic would be a start.
Attachments (2)
Change History (10)
comment:1 Changed 7 years ago by
Milestone: | 0.11 → 0.12 |
---|---|
Owner: | changed from Antoine Martin to Antoine Martin |
Status: | new → assigned |
comment:2 Changed 7 years ago by
Milestone: | 0.12 → future |
---|
I think that the win32 client has been very stable, which means this is a less of a priority.
Changed 7 years ago by
Attachment: | win32-invalid-quality-error.png added |
---|
shows the alert box for a command line parsing error on the "quality" option
Changed 7 years ago by
Attachment: | win32-encoding-help.png added |
---|
shows an alert box with some help text for a "help" command line option
comment:3 Changed 7 years ago by
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:
comment:4 Changed 7 years ago by
Milestone: | future → 0.15 |
---|
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
comment:6 Changed 6 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:8 Changed 6 weeks ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/392
too late for 0.11