Re: Lilypond taking forever to typeset

[David Kastrup]

Mojca Miklavec <address@hidden> writes:

> On 12 July 2016 at 13:25, David Kastrup <address@hidden> wrote:
>
>> Some backtrace that actually starts somewhere in LilyPond would be good.
>> So that would be a backtrace that actually ends somewhere in "main".
>
> I probably need to recompile lilypond with debug info then. Here are
> some more (useless?) traces:
>
> #0  0x99885a62 in read$NOCANCEL$UNIX2003 ()
> #1  0x9891aee6 in __sread ()
> #2  0x9891af0e in _sread ()
> #3  0x9891b465 in __srefill1 ()
> #4  0x9891c189 in __fread ()
> #5  0x9891c01f in fread ()
> #6  0x00b34045 in FT_Stream_EnterFrame ()
>
> #0  0x00b40bb6 in TT_Load_Simple_Glyph ()
> #1  0x00b47e62 in load_truetype_glyph ()
> #2  0x03818640 in ?? ()
> Previous frame inner to this frame (gdb could not unwind past this frame)
>
> #0  0x9988571e in open$NOCANCEL$UNIX2003 ()
> #1  0x99884a98 in open ()
> #2  0x988c62d9 in fopen ()
> #3  0x00b2e6ae in FT_Stream_Open ()

Ugh.  In ?? () does not even look like anything useful.  Seems like
LilyPond is not merely missing debug info but has its symbols stripped
as well.

> I don't see any viable alternative other than rewriting some portions
> to use the native system library calls to get information about fonts.

But that seems like something that Freetype2 rather than LilyPond should
be doing.  You can try pestering Werner either way I think.

-- 
David Kastrup