bug-lilypond
[Top][All Lists]
Advanced

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

Segfault when using \lookup?


From: Ophir Lifshitz
Subject: Segfault when using \lookup?
Date: Wed, 23 Dec 2015 02:25:49 -0500

Hello all,

I am trying to insert a few unencoded (but named) glyphs from an OpenType
font (i.e., glyphs not associated with a codepoint in the cmap table). I
haven't yet figured out if it's possible — if you know how, please tell me!

I ran lilypond 2.19.31 on the following example while investigating:

{ b'^\markup { \lookup #"a" } }


and the result was:

GNU LilyPond 2.19.31
Processing `foo.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...Segmentation fault: 11


When I changed #"a" to #"foobar" it compiled successfully.

After a bit of debugging, the dynamic cast seems to return null in
stencil-integral.cc
here
<http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=blob;f=lily/stencil-integral.cc#l676>.
Is it possible the case where fm is Pango_font instead of
Modified_font_metric is not handled? Is this a particularly straightforward
fix, or are more extensive modifications necessary?

Thanks,
Ophir


reply via email to

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