Better crash logging (tracking task)
Better crash logging helps users provide actionable bug reports. The easier we can make it for the easier, the better. Currently, it's not possible to get backtraces in multiple types of our releases, and even where it's possible to get backtraces, we're asking the users to run gdb manually.
We need to provide a way for users to get crash logs:
- Without using the command line
- Without installing additional things (symbols, gdb, etc.)
This is the tracking task, with these subtasks:
-
Can Windows builds get a backtrace? -
Can Linux AppImage builds get a backtrace? -
Can Linux Flatpak builds get a backtrace? - No, see #1535
-
Can Linux PPA builds get a backtrace? - Yes, if drkonqi is installed (Report Bug -> Developer Information, doesn't always work)
-
Can Mac (Intel) builds get a backtrace? - Yes, via the macOS crash reporter, but missing symbols for Kdenlive (see #1560)
-
Can Windows builds get MLT backtraces? -
Can Linux AppImage builds get MLT backtraces? -
Can Linux Flatpak builds get MLT backtraces? -
Can Linux PPA builds get MLT backtraces? - No, see #1537
-
Can Mac (Intel) builds get MLT backtraces? -
Save crash logs (including backtrace) to the disk -
Provide a GUI tool for viewing or retrieving the crash log (like Krita) -
Update user documentation on reporting bugs
Edited by Eric Jiang