About detecting source of a problem

classic Classic list List threaded Threaded
2 messages Options
Gülşah Köse Gülşah Köse
Reply | Threaded
Open this post in threaded view
|

About detecting source of a problem

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.


_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Bjoern Michaelsen Bjoern Michaelsen
Reply | Threaded
Open this post in threaded view
|

Re: About detecting source of a problem

Hi Gülşah,

On Mon, Feb 20, 2017 at 01:29:26PM +0300, Gülşah Köse wrote:
> Is there something I'm missing? Could you suggest another method I can use
> to detect the problem?
> [1] https://bugs.documentfoundation.org/show_bug.cgi?id=105982

Hmm, there are conflicting reports there on this being a regression. This:

 https://bugs.documentfoundation.org/show_bug.cgi?id=105982#c9

says there wasnt buggy behavior in 3.3, while:

 https://bugs.documentfoundation.org/show_bug.cgi?id=105982#c10

says 3.3.0 is buggy too. So would be good to clarify if this bug is indeed a
regression (that is: I used to work in LibreOffice 3.3.0). If so, it can be
bibisected (this is why there is a bibisectRequest keyword on the bug):

 https://wiki.documentfoundation.org/QA/Bibisect/Linux

Xisco (CC'ed) likely can help you out with the details.

Best,

Bjoern
_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice