https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66563
--- Comment #3 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> --- So, it seems Matthias is right, there is definitely a regression in gcc-4.9 in the code generation. Packages that were recently build with gcc-4.9_4.9.2-20 or newer tend to segfault. I noticed this with systemd, for example on tirpitz: systemd_220-2 works fine (compiled with gcc-4.9_4.9.2-10): root@tirpitz:~/systemd-test> journalctl --version systemd 220 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN root@tirpitz:~/systemd-test> systemd_220-6 segfaults (compiled with gcc-4.9_4.9.2-20): root@tirpitz:~/systemd-test> ./systemd/bin/journalctl --version systemd 220 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN Segmentation fault root@tirpitz:~/systemd-test> Attaching the strace for this segfault if that could be in any way helpful. Adrian
