Hi All, I thought this would be a good project for one (or more) of you fantastic documentation oriented people. Our debug page is not nearly as useful as it could be because it's written: (1) missing vital info; (2) in a way that is targeted towards developers instead of towards users - debugging often times isn't that hard and an "every day user" can do it but the instructions aren't the clearest.
If someone is interested in starting, I suggest starting with dealing with valgrind instructions, Norbert has been kind enough to say he'd explain the process to anyone from documentation that is willing to clean up the instructions. He can be found on the developer chat (shm_get) or by email [email protected]. Please don't waste his time if you're not going to take a serious stab at trying to clean the wiki One thing I've noticed is that there are several pages dealing with logs - they should be consolidated to the best location (in my opinion QA not development) and linked appropriately: https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_Valgrind_log https://wiki.documentfoundation.org/Development/How_to_debug#Valgrinding_.28memcheck.29_cppunit_tests https://wiki.documentfoundation.org/Development/How_to_debug#Valgrinding_.28memcheck.29_LibreOffice_itself etc.... I'm happy to talk about the scope of the clean up - feel free to ping me. Thanks in advance. Best, Joel -- To unsubscribe e-mail to: [email protected] Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/documentation/ All messages sent to this list will be publicly archived and cannot be deleted
