> I was also able to reproduce the issue only on the first run. When I
> observed the segfault, I wanted to run it again with a debugger
> attached but any subsequent run did not expose the issue.
Interesting. In the unstripped real-world use-case (namely, compiling
the LilyPond documentation) it fails every time.
Werner