[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 1791 in lilypond: footnote numbering is 'out of order' when us
Re: Issue 1791 in lilypond: footnote numbering is 'out of order' when using multiple staves in a system
Wed, 12 Oct 2011 08:38:26 +0000
Comment #7 on issue 1791 by address@hidden: footnote numbering is 'out of
order' when using multiple staves in a system
Now, the patch changes the visual output in a woodwind diagram patch and
issues several warning messages.
However, when I compile all of these files outside of the regtests, these
messages aren't issued.
Furthermore, I put a load of pretty prints in every function that this
patch changes and not one of them is called (or it is called but does not
enter the interior loop). Specifically, grob2D is never called, and this
is the only function that does any heavy lifting.
I am thinking, then, that this problem has to do with garbage collection /
an uninitialized variable. Thus, I need to be able to do two things:
1) Replicate the results from the regtests. What type of paper bloc do I
need to add and what options to do I need to invoke to do this?
2) Once replicated, is there a way to use valgrind to have LilyPond exit as
soon as it functions differently? That is, launch a "normal" version of
the program and have valgrind issue a log file of all the function calls.
Then, launch a different version with the patch applied and have valgrind
complain as soon as there is a function call that wasn't there before (or,
even better, keep an intelligent record of performance divergences). This
is likely the only way I'll be able to track down the problem.