https://bugs.documentfoundation.org/show_bug.cgi?id=127826
--- Comment #10 from Buovjaga <ilmari.lauhakan...@libreoffice.org> ---
(In reply to stdedos from comment #9)
> (In reply to Buovjaga from comment #8)
> > You can use a debug build (-dbg) and try to get a backtrace of the crash:
> > https://dev-builds.libreoffice.org/daily/master/current.html
> > https://wiki.documentfoundation.org/Installing_in_parallel/Linux
> > https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.
> > 2FLinux:_How_to_get_a_backtrace
>
> Is it that complicated to promote bare-bones backtrace capabilities to
> production packages?
No. You can check, if your Xenial PPA provides debug symbol packgages as well.
At least Ubuntu's non-PPA packages do.
> As I said,
>
> > Please keep in mind, that the only versions I am considering testing would
> > be:
> > * The latest available on a Xenial PPA
> > * The latest available on snap
> > * The latest available on AppImage
>
> and I don't understand why I have to do the extra 10s of miles to
> side-by-side install a debug build to triangulate a rare bug. I have a very
> niche use-case for Calc, which I don't want to de-stabilize even more from
> getting master@daily
>From what I remember, the dbg builds don't require any extra miles. You just
have to extract the archive and then you can run program/soffice
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
