When emerging XFree86, xcursorgen segfaults when using gcc-3.3.2-r7 when compiled with -O2. Reproducible: Always Steps to Reproduce: 1. Emerge libpng with -O2 in the CFLAGS 2. Attempt to emerge xfree 3. Wait long enough for xcursorgen to be used Actual Results: Segfault on the commandline: LD_LIBRARY_PATH=../../../exports/lib ../../../exports/bin/xcursorgen ... in directory redglass Portage 2.0.50-r8 (default-ppc-2004.1, gcc-3.3.2, glibc-2.3.3.20040420-r0, 2.6.4-pegasos0) =============================================================== == System uname: 2.6.4-pegasos0 ppc 740/750 Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.58-r1 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="ppc" AUTOCLEAN="yes" CFLAGS="-O2 -mcpu=750 -pipe -fsigned-char -mpowerpc-gfxopt" CHOST="powerpc-unknown-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb/rules /usr/kde/2/share/config /usr/kde/3/share/ config /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O2 -mcpu=750 -pipe -fsigned-char -mpowerpc-gfxopt" DISTDIR="/usr/portage/distfiles" FEATURES="ccache" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://www.ibiblio.org/pub/Linux/distributions/ gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X acl alsa berkdb caps cups directfb dvd esd fbcon foomaticdb gatos gdbm gif gnome gnome- libs gpm gtk gtk2 imap imlib jpeg kde krb4 ldap libwww mitshm motif mozilla nls offensive oggvorbis opengl oss pam perl png ppc python qt readline samba sasl sdl slang slp socks5 ssl tcpd truetype xv"
Happened to me on PPC32 after upgrading to gcc 3.3.3 The problem is with setjmp, rebuilding linpng with the same compiler as xorg (and htmldoc and other apps using png with setjmp fixed the problem).
not really an X11 bug
try the suggested workaround
*** Bug 53968 has been marked as a duplicate of this bug. ***
*** Bug 70688 has been marked as a duplicate of this bug. ***