Re: lilypond crash in special case
On Tue, Mar 31, 2015 at 7:29 PM, Thomas Morley wrote: > 2015-03-31 16:54 GMT+02:00 Simon Albrecht : > > Am 31.03.2015 um 14:59 schrieb Phil Holmes: > >> > >> "Leo Naab" wrote in message > >> news:loom.20150331t133343-...@post.gmane.org... > > >>> I have a special lilypond file with let's lilypond.exe crash. The file > >>> works > >>> fine with version 2.19.15, but not with 2.19.17. > >>> > >>> The crash has do to with a "\new Lyric" line. "\new Lyric" in \context > >>> Staff > >>> didn't work, but if the "\new Lyric" comes behind the \context Staff > all > >>> is > >>> fine. > > > > Submitted as Issue 4339. Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond crash in special case
2015-03-31 16:54 GMT+02:00 Simon Albrecht :
> Am 31.03.2015 um 14:59 schrieb Phil Holmes:
>>
>> "Leo Naab" wrote in message
>> news:loom.20150331t133343-...@post.gmane.org...
I'm not top posting.
>>>
>>>
>>> I have a special lilypond file with let's lilypond.exe crash. The file
>>> works
>>> fine with version 2.19.15, but not with 2.19.17.
>>>
>>> The crash has do to with a "\new Lyric" line. "\new Lyric" in \context
>>> Staff
>>> didn't work, but if the "\new Lyric" comes behind the \context Staff all
>>> is
>>> fine.
>>>
>>> I reduce my lilypond file to the following:
>>
>>
>> I can confirm this also crashes on 2.19.16, Windows. I get the following
>> error:
>>
>> :11:72: programming error: Spanner `TieColumn' is not fully contained in
>> parent spanner. Ignoring orphaned part
>> a4 a8 g8~ g8 g4 fis8~ fis8 fis4. r8 g8 g8 g8 a4 a8 ais8~ ais8 ais4 fis8
>> ~ \break
>>
> Same on ubuntu.
> ~ Simon
>
A minimal example triggering it:
\version "2.19.17"
<<
\new Staff \new Voice { r1 }
\new Staff
<<
\new Voice = "bass" { a1~ \break a1 }
% comment this line and uncomment the line below then it work's
\new Lyrics \lyricsto "bass" { bla }
>>
%\new Lyrics \lyricsto "bass" { bla }
>>
The combination of a dying Staff at linebreak, whereas the other has a
Tie and assigned Lyrics is needed to have the crash
Cheers,
Harm
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond crash in special case
Am 31.03.2015 um 14:59 schrieb Phil Holmes: "Leo Naab" wrote in message news:loom.20150331t133343-...@post.gmane.org... I'm not top posting. I have a special lilypond file with let's lilypond.exe crash. The file works fine with version 2.19.15, but not with 2.19.17. The crash has do to with a "\new Lyric" line. "\new Lyric" in \context Staff didn't work, but if the "\new Lyric" comes behind the \context Staff all is fine. I reduce my lilypond file to the following: I can confirm this also crashes on 2.19.16, Windows. I get the following error: :11:72: programming error: Spanner `TieColumn' is not fully contained in parent spanner. Ignoring orphaned part a4 a8 g8~ g8 g4 fis8~ fis8 fis4. r8 g8 g8 g8 a4 a8 ais8~ ais8 ais4 fis8 ~ \break Same on ubuntu. ~ Simon ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond crash in special case
"Leo Naab" wrote in message news:loom.20150331t133343-...@post.gmane.org... I'm not top posting. I have a special lilypond file with let's lilypond.exe crash. The file works fine with version 2.19.15, but not with 2.19.17. The crash has do to with a "\new Lyric" line. "\new Lyric" in \context Staff didn't work, but if the "\new Lyric" comes behind the \context Staff all is fine. I reduce my lilypond file to the following: I can confirm this also crashes on 2.19.16, Windows. I get the following error: :11:72: programming error: Spanner `TieColumn' is not fully contained in parent spanner. Ignoring orphaned part a4 a8 g8~ g8 g4 fis8~ fis8 fis4. r8 g8 g8 g8 a4 a8 ais8~ ais8 ais4 fis8 ~ \break -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
lilypond crash in special case
> I'm not top posting.
I have a special lilypond file with let's lilypond.exe crash. The file works
fine with version 2.19.15, but not with 2.19.17.
The crash has do to with a "\new Lyric" line. "\new Lyric" in \context Staff
didn't work, but if the "\new Lyric" comes behind the \context Staff all is
fine.
I reduce my lilypond file to the following:
\version "2.19.0"
sopranMusic = \relative c' {
%fis1 e1 fis1
r1 r1 r1
}
bassMusic = \relative c'' {
%e2~ e4.( fis8 ~ fis1) g2( a4. d,8) \break
a4 a8 g8~ g8 g4 fis8~ fis8 fis4. r8 g8 g8 g8 a4 a8 ais8~ ais8 ais4
fis8~ \break
fis1 a1 fis1 a1
}
bassWords = \lyricmode {
%uh uh
Er ist das Zen -- trum der Ge -- schich -- te. er ist der An -- ker
}
\new ChoirStaff <<
\context Staff = "Sopran" <<
\new Voice = "Sopran" {
\sopranMusic
}
>>
\context Staff = "Bass" <<
\new Voice = "Bass" {
\bassMusic
}
% comment this line and uncomment the line below then it work's
\new Lyrics \lyricsto "Bass" \bassWords
>>
%\new Lyrics \lyricsto "Bass" \bassWords
>>
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
