https://bugs.documentfoundation.org/show_bug.cgi?id=95039
--- Comment #12 from Beluga <[email protected]> --- (In reply to helplibreoffice from comment #11) > If you actually took a moment to read the bug report I filed, you would > understand that providing a trace is impossible as is providing a document > that will reliably reproduce the bug. > > I have taken my time to accurately and extensively provide every detail I > could in order to help this project. If we assume you had been able to get it to crash again, I don't see why getting a backtrace would have been impossible. If we assume that you will not be able to get it to crash ever again, then this report will lead nowhere and such weird crashes are best left to the crashtesting VM and fuzzers and such. You can read more about those in these links: https://mmohrhard.wordpress.com/2013/04/19/automated-import-crash-testing-in-libreoffice/ http://caolanm.blogspot.com/2015/10/finding-ui-crashes-by-fuzzing-input.html It is untenable that you ask us to behave in a certain way or you will start painting LibreOffice black. You know you can always come back to this report, add new findings and open it again, so why resort to threats? -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
