Bug#866129: lilypond: segfault using lilypond buster testing

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#866129: lilypond: segfault using lilypond buster testing

Antonio Ospite-2
Package: lilypond
Version: 2.18.2-7
Followup-For: Bug #866129

Dear Maintainer,

lilyopnd devs suggest[1] that this could be an issue with gcc-6,
reported in the issue 4814 on sf.net[2], which has been fixed by commit
b0dce76daf27 (Issue 4814: grob.cc segfaults with gcc6)[3].

[1] http://lists.gnu.org/archive/html/lilypond-devel/2017-06/msg00165.html
[2] https://sourceforge.net/p/testlilyissues/issues/4814/?page=1
[3] http://git.savannah.gnu.org/cgit/lilypond.git/commit/?id=b0dce76daf27721ba157cd2ac5d7662d4c8d75f8

I cannot verify this anytime soon but maybe the provided info could help
someone else to check if the problem is actually related to Issue 4814.

Can the OP send a backtrace?

Ciao,
   Antonio

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (500, 'unstable-debug')
Architecture: amd64 (x86_64)

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

-- no debconf information
--
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?

Reply | Threaded
Open this post in threaded view
|

Bug#866129: lilypond: segfault using lilypond buster testing

Don Armstrong-2
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
>      ineffective)?
>    * What was the outcome of this action?
>    * What outcome did you expect instead?

On Tue, 27 Jun 2017, Antonio Ospite wrote:
> lilyopnd devs suggest[1] that this could be an issue with gcc-6,
> reported in the issue 4814 on sf.net[2], which has been fixed by commit
> b0dce76daf27 (Issue 4814: grob.cc segfaults with gcc6)[3].

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.


--
Don Armstrong                      https://www.donarmstrong.com

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_