Emerging gnomad-2 with the -O3 in your CFLAGS will compile an unusable program. Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: Upon launching gnomad-2 it throws an error that asks you to restart the application or quit. Expected Results: gnomad-2 runs normally. Portage 2.0.51-r3 (default-linux/x86/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.9-gentoo-r6 i686) ================================================================= System uname: 2.6.9-gentoo-r6 i686 mobile AMD Athlon(tm) 4 Processor Gentoo Base System version 1.6.6 Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.92.0.2-r1 Headers: sys-kernel/linux26-headers-2.6.8.1-r1 Libtools: sys-devel/libtool-1.5.2-r7 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-4 -O3 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon-4 -O3 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="http://gentoo.osuosl.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="3dnow X acpi alsa apm avi berkdb bitmap-fonts crypt dga directfb dmx dvd dvdr dvdread encode f77 fam foomaticdb fortran gdbm gif glut gpm gtk gtk2 imlib java jpeg libg++ libwww mad mikmod mmx mng motif mpeg nas ncurses nls nptl oggvorbis opengl pam pdflib perl png python quicktime readline real sdl spell ssl svg svga tcpd tiff truetype x86 xml2 xmms xv xvid zlib"
Created attachment 44969 [details, diff] Strips unsafe -O? flags from CFLAGS
if you want to take my suggestion (which has helped me), then... relax your C FLAGS to '-march=athlon-4 -O2 -mno-sse' and recompile everything on your box 'emerge -e world'. then give us a backtrace. (gdb /usr/bin/whatever; run; make it go boom, and then 'bt full') this is probably the movaps disaster bug. movaps on non-sixteen-byte aligned memory, affects gcc 3.4.x compiled programs especially. not planned to be fixed in gcc mainline for some time. disabling SSE code generation has fixed a host of troubles for me (i use gcc 3.4.x too).
please pick up jnc's suggestion, afterwards provide the gdb backtrace. thanks
