[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] segfaults (with GCC6?)

From: Valentin Villenave
Subject: segfaults (with GCC6?)
Date: Fri, 25 Mar 2016 08:59:38 +0100

Greetings everybody,
I’m having a weird segfault on several regtests (and most of my own ly
files, which is annoying):

Interpreting music...
Preprocessing graphical objects...
Program received signal SIGSEGV, Segmentation fault.
0x0000000000496c2f in Grob::get_offset (address@hidden,
address@hidden) at
400       if (dim_cache_[a].offset_)

Here are the regtests that reproduce the bug (the others compile just fine):

What makes is weird is that the bug happens both with my LilyPond
build (latest master branch) *and* with my distribution’s package
(Fedora repos generally have the latest development release: as of now
it’s 2.19.38 but this also happened with .37 and .36); however, GUB
packages of the exact same development release, don’t reproduce the

Could it be because Fedora 24 is using GCC6? Here’s what gcc -v tells me:

Target: x86_64-redhat-linux
Configured with: ../configure --enable-bootstrap
--enable-languages=c,c++,objc,obj-c++,fortran,ada,go,lto --prefix=/usr
--mandir=/usr/share/man --infodir=/usr/share/info
--with-bugurl= --enable-shared
--enable-threads=posix --enable-checking=release --enable-multilib
--with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-gnu-unique-object
--enable-linker-build-id --with-linker-hash-style=gnu --enable-plugin
--enable-initfini-array --disable-libgcj --with-isl --enable-libmpx
--enable-gnu-indirect-function --with-tune=generic --with-arch_32=i686
Thread model: posix
gcc version 6.0.0 20160305 (Red Hat 6.0.0-0.15) (GCC)

Now, granted, Fedora 24 is in a very early state and some other
programs do tend to crash from time to time (Firefox with JS-intensive
pages, for example). But LilyPond is the only one I have where such
segfaults are 100% reproducible.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]