Comment #7 on issue 2335 by [email protected]: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
That's basically useless: looks like you have binaries without debug
symbols. Do have a way to compile the code yourself? If that were
possible, one could at least try to figure out the responsible commit. If
we look at
git log --oneline release/2.15.22-1..release/2.15.23-1
and cut out everything improbable (according to my personal metrics) we get
to
7ce94ab Prevents cross-staff Stems from colliding with articulations.
968e472 Looser spacing for ragged-last-bottom; issue 1377
ff72533 hairpin.cc: transition between spanners aligns on note; issue 1216
99ef1a8 Updates version string in span-bar-articulation.
f417a60 Implements padding at right-broken hairpins that come up against
span ba
5543eb5 Prevents scripts in cross-staff contexts from colliding with span
bars.
3bcfd69 Prevents dynamics from colliding with cross-staff stems.
The first one would likely be related to articulate.ly, but then
articulate.ly is good for a lot of spacing changes.
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
