bug-lilypond
[Top][All Lists]
Advanced

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

Re: Core dump for tremolo


From: David Kastrup
Subject: Re: Core dump for tremolo
Date: Sat, 16 Sep 2017 09:26:52 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux)

Knut Petersen <address@hidden> writes:

> 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.

Ok, so I was wrong about that.  Do we have an issue tracked for it?
"This is still an issue of current master" implies that this is not the
first time this has been brought up.

-- 
David Kastrup



reply via email to

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