[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 2393 in lilypond: Segfault in connection with \markuplist
From: |
lilypond |
Subject: |
Re: Issue 2393 in lilypond: Segfault in connection with \markuplist |
Date: |
Mon, 12 Mar 2012 11:49:20 +0000 |
Comment #5 on issue 2393 by address@hidden: Segfault in connection with
\markuplist
http://code.google.com/p/lilypond/issues/detail?id=2393
So this is not a regression. That's good news for 2.16 release planning.
Still needs to get investigated.
#(display #{ \markuplist \bold { \wordwrap-lines { } } #})
outputs
((#<procedure bold-markup (layout props arg)> (#<procedure
wordwrap-lines-markup-list (layout props args)> ())))
I would assume that this is not a valid markup list.
Unwrapping the list leads to
\markup \bold { \wordwrap-lines { } }
as a test case. This is accepted and leads to an error message in
processing:
Parsing.../usr/local/share/lilypond/2.15.31/scm/define-markup-commands.scm:1118:6:
In
procedure ly:stencil-empty? in expression (remove ly:stencil-empty?
stencils):
/usr/local/share/lilypond/2.15.31/scm/define-markup-commands.scm:1118:6:
Wrong type argument in position 1 (expecting Stencil): (#<Stencil >)
That seems to be the same problem: a markup list (or stencil list) where a
markup is expected.
- Issue 2393 in lilypond: Segfault in connection with \markuplist, lilypond, 2012/03/12
- Re: Issue 2393 in lilypond: Segfault in connection with \markuplist, lilypond, 2012/03/12
- Re: Issue 2393 in lilypond: Segfault in connection with \markuplist, lilypond, 2012/03/12
- Re: Issue 2393 in lilypond: Segfault in connection with \markuplist, lilypond, 2012/03/12
- Re: Issue 2393 in lilypond: Segfault in connection with \markuplist, lilypond, 2012/03/12
- Re: Issue 2393 in lilypond: Segfault in connection with \markuplist,
lilypond <=
- Re: Issue 2393 in lilypond: Segfault in connection with \markuplist, lilypond, 2012/03/12