On Tue, Jan 29, 2019 at 12:54 AM Matthias Seidel <matthias.sei...@hamburg.de> wrote:
> Hi all, > > The crash report tool was abandoned some years ago. Help files were > removed in 2014: > https://bz.apache.org/ooo/show_bug.cgi?id=125696 > > Now I simply removed the directory main/crashrep from my build tree > (AOO42X) and still could build successfully. > > So my question is, can it be safely removed? That would free some space > and remove unused strings for translation. > > My vote would be: ABSOLUTELY NOT! This is C++, there is no Exception.printStackTrace() when things go wrong, there is no cross-platform remote debugging. What are we going to do when users come back to us crying how "it crashed"? With a stack trace, we know where to look, and even if there are no debug symbols, we at least know which module crashed. Without a stack trace, the best we can hope for is to reproduce the problem ourselves while running in a debugger. We absolutely need a user-friendly crash reporter, especially after so many changes, with the upcoming Win64 port, with the port to newer MSVC, and many other changes that will destabilize the codebase further. Yes the crashreporter tool wasn't great, it didn't work on Mac, it required some webservice to submit reports to, but so what? It's just code. We could just make it print a textual report that users can copy and paste into Bugzilla. That crashreporter stands between us and chaos. Prior threads discussing it: 29 May 2012 “How to enable crash log for AOO3.4?” http://mail-archives.apache.org/mod_mbox/openoffice-dev/201205.mbox/%3cCAGSaLEqZaw12nYE089iDRJY=bb0axqujepnadvg25vrw0ln...@mail.gmail.com%3e 22 October 2014 “crash reporter -- can someone supply commit information on this?” http://mail-archives.apache.org/mod_mbox/openoffice-dev/201410.mbox/%3C544838E3.6050600%40gmail.com%3E Regards Damjan
