On 02/09/16 17:31, David Kastrup wrote:
Timothy Lanfear <timo...@lanfear.me> writes:Bug appears in 2.19.46 and .47. Ubuntu 16.04, 64-bit. The first line provokes a core dump. The second line is perhaps the right syntax for this construction and works fine, but I'm reporting in case there is something here that needs investigating. \version "2.19.46" { <b' gis'>2\fermata ~ b'2 % core dump <b'~ gis'>2\fermata b'2 % move tie inside chord, OK <b' g'>2\fermata ~ b'2 % gis => g, OK <b' gis'>2 ~ b'2 % delete fermata, OK <b' gis'>2\fermata b'2 % delete tie, OK }Not here. Which compilations are you using? I suspect some compiler bug or overoptimization.
I'm using the pre-built package. lanfear@D20$ /usr/local/lilypond-2.19.46/bin/lilypond tmp.ly GNU LilyPond 2.19.46 Processing `tmp.ly' Parsing... Interpreting music... Preprocessing graphical objects...Segmentation fault (core dumped) -- Timothy Lanfear, Bristol, UK. _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
