https://bugs.documentfoundation.org/show_bug.cgi?id=126488
V Stuart Foote <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #31 from V Stuart Foote <[email protected]> ---
There is no functional use of the Breakbad generated crash dumps without
corretly linked symbols. They need to be present locally or on the project
crashreport server--which we won't/can't do.
Like Dieter, agree the crash report dialog should be fully suppressed. The
partial dialog now on recovery is only confusing for folks on dev builds of
master that do not contain the "--enable-breakpad" build string.
Fully suppressing the dialog for dev builds is a valid issue.
The other concerns here are better handled by improving guidance for working
with debug builds and local symbol cache [refs].
For dev builds, dumping Breakpad reports in bulk back to a central service is
no substitute to a few well crafted backtraces once details of a crash with
steps-to-reproduce (STR) have been reported.
Crafting the backtrace locally allows each user to account for the actions they
take to reproduce the issue with refined STR.
=-refs-=
https://wiki.documentfoundation.org/Development/How_to_debug
https://wiki.documentfoundation.org/QA/BugReport/Debug_Information
https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
