Re: Segmentation Fault in 2.18 (was Re: Learn from Finale 2014 (seriously)?)

[Paul Scott]

On Thu, Feb 27, 2014 at 10:27:53AM +0000, Richard Shann wrote:
> I just came across a workaround for this LilyPond crash - adding

I have been getting very occasional segfaults with Lily since at 
least 2.17.  I have never been able to create a minimal example 
because as soon as I change anything the code works fine.

Paul Scott

> 
> \once \override MultiMeasureRestNumber #'transparent = ##t
> 
> before the multi-measure rests in the second voice results in the
> typesetting finishing correctly.
> 
> I came across this because I was getting the number printed twice in
> some circumstances (even though the rest was only printed once), and
> this fixed that bug.
> 
> The only remaining tweak is to adjust the vertical positioning of the
> multi-measure rest, then Denemo will have a complete package of commands
> for printing a score and parts where some parts have multi-measure rests
> that are shared.
> 
> Richard
> 
> 
> On Sat, 2014-02-01 at 15:04 +0000, Richard Shann wrote:
> > On Thu, 2013-11-14 at 21:14 +0100, Jan-Peter Voigt wrote:
> > > On 14.11.2013 16:19, Joseph Rushton Wakeling wrote:
> > > >> there is an update of this snippet in the mail archives and I will post
> > > >> my version later.
> > > >
> > > > Fantastic, thank you! :-) 
> > > so, here is the version I regularly use ... in fact, this is taken from
> > > some e-mail on this list some time ago. It also merges MultiMeasure rests.
> > 
> > I was just putting this code into Denemo and I noticed it merged a
> > multi-measure rest in the top voice with a sequence of whole measure
> > rests in the second voice, but it caused a segmentation fault in
> > LilyPond when it tries to merge multi measure rests from both voices.
> > 
> > The test file that shows this is attached. The include file is also
> > attached, it is the mergeRests.ly from the original message with the
> > example removed and convert-ly run on it to update it from 2.16.1 - the
> > resultant version reads 2.17.97 which I recall is a known bug.
> > 
> > I guess this part of the thread needs to switch to lilypond-devel or
> > lilypond-bug, now - I originally started this email just to enquire
> > about merging multi-measure rests ...
> > 
> > Richard
> > 
> > 
> > 
> > 
> > _______________________________________________
> > lilypond-user mailing list
> > address@hidden
> > https://lists.gnu.org/mailman/listinfo/lilypond-user
> 
> 
> 
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>