Re: Core dump for tremolo

[Knut Petersen]

Am 15.09.2017 um 23:20 schrieb David Kastrup:
> > > > \version "2.19.39"
> > > >
> > > > \relative c' {
> > > >       c8:32 c32 c c c
> > > > }
> > > >
> > > > Preprocessing graphical objects...lilypond:
> > > > /home/gub/NewGub/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/flower/include/interval.hh:227:
> > > > T Interval_t<T>::center() const [with T = double]: Assertion `!is_empty ()'
> > > > failed.
> > > > Aborted (core dumped)
> > > >
> > > > Rutger Hofman
> > > > Amsterdam
> > This is still an issue of current master ... has anybody investigated
> > the problem ?
> I don't know whether we have an issue in the tracker for this, but it
> will always be an issue since there is no valid output for this input
> (I don't think one can have both a flag and a stem tremolo).

Well, we actually can have both a flag and a stem tremolo. Add \autoBeamOff to 
Rutger's mwe, it will compile and give an output with flag and tremolo.

In some cases we even can have a beam and a stem repeat on one note:

\version "2.21.0"
\relative c' {  c8 c32 c c c c8 c c c c8:32 c32 [c c c] }

Of course, autobeaming is painfully wrong here.

>   Aborting with a core dump (and a cryptic message not obviously related to the 
> input) is of course about the worst possible diagnostic,
I agree.

> but we would not be able to produce valid graphics either.
No. There is a solution for this input, but lilypond fails miserably.

Knut

Berg_Lulu_Adagio_Bar155.jpg
Description: JPEG image