Marc Hohl <[email protected]> writes:
> Am 24.11.2015 um 00:12 schrieb Thomas Morley:
> [...]
>>
>> So,
>> commit b416f10429d8d3881445d9000ff422dc67176df1
>> Author: David Kastrup <[email protected]>
>> Date: Wed Jul 15 23:30:30 2015 +0200
>>
>> Issue 3693: Let Percent_repeat_iterator be unfazed by Timing changes
>>
>> There is still one shortcoming: the percent repeats will not contain any
>> material apart from the percent itself. In particular, no Timing
>> changes will be repeated. If there are meter changes or \partial
>> commands inside of percent repeats, they need to occur in parallel
>> passages outside of any percent repeat, if necessary in a separate
>> "timing track".
>>
>> is indeed the problem.
>
> Thanks for your work on this issue!
And for me in creating it.
>> Now it would be nice I'd could come up with a tiny example...
>>
>> Though, very strange things happen, like:
>>
>> assume file-1.ly with
>>
>> foo = { some-music }
>> buzz = { some-other-music }
>>
>> and
>>
>> file-2.ly with
>>
>> \include "file-1.ly"
>> \score {
>> <<
>> \new Staff \foo
>> \new Staff \buzz
>> >>
>>
>> compiling file-2.ly causes a segfault.
>> commenting \new Staff \buzz still causes a segfault
>> additional commenting(!!!!!) buzz = { some-other-music } in file-1.ly,
>> and the segfault disappears!!!
>> But it's not consistent! It depends what else is defined in those files.
>
> Yep. Moreover, if I removed some notes from buzz, the segfault
> disappeared, but adding one single note causes Lilypond to crash,
> and we talk about scores with 3-5 pages or even less.
Garbage collection errors tend to behave somewhat erratically.
Ticket created at: https://sourceforge.net/rest/p/testlilyissues/issues/4670/
--
David Kastrup
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user
