Kernel: Linux 4.11.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8), LANGUAGE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages lilypond depends on:
ii ghostscript 9.21~dfsg-1
ii libc6 2.24-12
ii libfontconfig1 2.12.3-0.1
ii libfreetype6 2.6.3-3.2
ii libgcc1 1:7.1.0-7
ii libglib2.0-0 2.52.3-1
ii libgmp10 2:6.1.2+dfsg-1
ii libltdl7 2.4.6-2
ii libpango-1.0-0 1.40.5-1
ii libpangoft2-1.0-0 1.40.5-1
ii libstdc++6 7.1.0-7
ii lilypond-data 2.18.2-7
ii python 2.7.13-2
Versions of packages lilypond recommends:
ii texlive-latex-base 2017.20170623-1
Versions of packages lilypond suggests:
ii lilypond-doc 2.18.2-7
Bug#866129: lilypond: segfault using lilypond buster testing
Control: forcemerge 871372 -1
On Tue, 27 Jun 2017, Thomas Wille wrote:
> *** Reporter, please consider answering these questions, where appropriate ***
> * What led up to the situation?
> * What exactly did you do (or not do) that was effective (or
> * What was the outcome of this action?
> * What outcome did you expect instead?
On Tue, 27 Jun 2017, Antonio Ospite wrote:
> lilyopnd devs suggest that this could be an issue with gcc-6,
> reported in the issue 4814 on sf.net, which has been fixed by commit
> b0dce76daf27 (Issue 4814: grob.cc segfaults with gcc6).
Thanks for the report; I've confirmed that this is this issue, and I'm
just about ready to roll out an update for it.
The major difference between a thing that might go wrong and a thing
that cannot possibly go wrong is that when a thing that cannot
possibly go wrong goes wrong it usually turns out to be impossible to
get at or repair.
-- Douglas Adams _Mostly Harmless_