About detecting source of a problem

Gülşah Köse gulsah.1004 at gmail.com
Mon Feb 20 10:29:26 UTC 2017


Dear developers,

I'm trying to find the source of LibreOffice's problematic behavior. I
applied all the methods I knew to detect source of problem and could not
reach a conclusion.
I think there must be other methods that I do not know. I know every bug is
unique, but I think it is something I will learn from this bug and i need
your experiences.

Here are the methods I use to detect the source of the problem[1]:

1. The document is free from unnecessary information as much as possible.
2. Compile LibreOffice(last developmen version) with --enable-debug mode
and observe standard output while reproducing the problem.
3. If possible to walk around and produce a smooth document, compare the
problematic and problem-free document xml files.
4. Investigate whether there is an article written about the problematic
feature.
5. Examine the probable key words in the source code and examine the
information in the suspected parts in debug mode.

For the following bug[1]:

1. Done
2. Done. There is no related output
3. For this bug it is posibble to produce problem-free document with same
reproducement steps. (Inconsistent behavior) Compared:  Exactly same xml
files.
4. Researched printing a file, print preview, render, WYSWYG, cell margin,
spacing, padding,... subjects.
5. Grepped cell margin, spacing, padding, SID_PRINTPREVIEW keywords

Is there something I'm missing? Could you suggest another method I can use
to detect the problem?

Thank you in advance.

[1] https://bugs.documentfoundation.org/show_bug.cgi?id=105982


-- 
Gülşah Köse
about.me/gulsahkose
* <http://about.me/gulsahkose>*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice/attachments/20170220/76e62f90/attachment.html>


More information about the LibreOffice mailing list