bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Crash with simultaneous-duplicating music function and onceoffset


From: James Lowe
Subject: Re: Crash with simultaneous-duplicating music function and onceoffset
Date: Mon, 16 Jul 2018 06:46:24 +0100 (BST)

Hello,

On Sun, 15 Jul 2018 20:09:52 -0700, Aaron Hill <address@hidden> wrote:

> On 2018-07-15 18:21, Simon Albrecht wrote:
> > Hello everybody,
> > 
> > this combination of a custom music function that combines the music
> > simultaneously with itself and a \once\offset command causes LilyPond
> > to crash (exit with return code 11):
> > 
> > %%%%%%%%%%%%
> > \version "2.19.82"
> > test =
> > #(define-music-function (parser location mus) (ly:music?)
> >   #{ << $mus $mus >> #})
> > 
> > \test { \once\offset length 1 Stem 4 }
> > %%%%%%%%%%%%
> 
> Seems the custom music function is not needed to reproduce a crash.
> 
> %%%%
>    \version "2.19.82"
>    music = { \once \offset length 5 Stem 4 4 }
>    << \music \music >>
> %%%%
> 
> This also results in:
> 
> > GNU LilyPond 2.19.82
> > Processing `crash.ly'
> > Parsing...
> > Interpreting music...
> > Preprocessing graphical objects...
> > fish: “lilypond crash.ly” terminated by signal SIGSEGV (Address 
> > boundary error)

...

> 
> -- Aaron Hill

I created https://sourceforge.net/p/testlilyissues/issues/5383/ for this crash 
report.


James


reply via email to

[Prev in Thread] Current Thread [Next in Thread]