Re: Segfault with multimeasure rests and metronome markings

[James Bailey]

On Dec 27, 2010, at 6:49 PM, Chris Snyder wrote:

> We've run into a segfault in all versions of LilyPond after 2.13.32, 
> including 2.13.44. I've narrowed it down to occur when a tempo marking is 
> placed over a multimeasure rest when the Metronome_mark_engraver has been 
> added to the staff containing the rest:
> 
> ----
> 
> \version "2.13.44"
> % works in 2.13.32 and prior
> 
> \score {
>       \new Staff {
>               \tempo 4=150
>               R1 |
>       }
>       \layout {
>               \context {
>                       \Score
>                       \remove "Metronome_mark_engraver"
>                       \remove "Staff_collecting_engraver"
>               }
>               \context {
>                       \Staff
>                       \consists "Metronome_mark_engraver"
>                       \consists "Staff_collecting_engraver"
>               }
>       }
> }
> 
> ----
> 
> Console output:
> 
> Processing `RestSegfault.ly'
> Parsing...
> Interpreting music...
> Preprocessing graphical objects.../home/csnyder/bin/ly-choose: line 29:  7328 
> Segmentation fault      $ly $*
> LilyPond [RestSegfault.ly] exited with return code 139.
> 
> (ly-choose is my own wrapper script to run the version of LilyPond specified 
> in the \version parameter; the segfault still occurs when this script is not 
> used)
> 
> I'm running Kubuntu 10.10 64-bit using the official LilyPond binaries.
> 
> Thanks,
> Chris
> 
> -- 
> Chris Snyder
> Adoro Music Publishing
> (616) 828-4436
> www.adoromusicpub.com
> 
> _______________________________________________
> bug-lilypond mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/bug-lilypond

Thanks, added as issue 1464