On 12.04.2015 21:25, Joel Madero wrote: > There is a bug that needs some advanced QA work on it and I'm curious if > anyone wants to take a stab at it and try to document the process > (including screenshots and/or screen captures). > > https://bugs.documentfoundation.org/show_bug.cgi?id=75554 > > Comment 6 describes what Michael needs.
AFAICS there are three major techniques addressed: 1) bibisecting the problem 2) reducing the document 3) stack tracing with debugging symbols Techniques 1 + 3 are described in detail in the wiki: 1) https://wiki.documentfoundation.org/Bibisect 3) https://wiki.documentfoundation.org/Development/How_to_debug and also for Windows: https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg Technique 2, reducing the document, should be easy to do IMHO (though tedious for big/complex documents): just remove all the objects from the document one by one and at each step look if the problematic behavior is still reproducible. As a first test, you can copy all contents from the problematic document into a new document to exclude that there is some (old/inherited) flaw in the document structure. Nino _______________________________________________ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
