Please update sys-kernl/ppc64-headers. There is at least one bug in /usr/include/asm/ptrace.h Here, we find: #define PT_FPSCR (PT_FPR0 + 32 + 1) when it's defined with: #define PT_FPSCR (PT_FPR0 + 32) in recent kernels. This prevent gdb to work well as it gets EIO while trying to retrieve this register. I'm running a linux-2.6.10-rc2 kernel with patches to make it run on the new Imac G5. Refer to http://bugs.gentoo.org/show_bug.cgi?id=68970 for more infos on the used patchset (but I can assure it changes nothing to ptrace behaviour). Reproducible: Always Steps to Reproduce: 1. 2. 3. Gentoo Base System version 1.6.6 Portage 2.0.51-r3 (default-ppc64-2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6 .10-rc2-rtc ppc64) ================================================================= System uname: 2.6.10-rc2-rtc ppc64 PPC970FX, altivec supported ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.91.0.1 Headers: sys-kernel/ppc64-headers-2.6.4 Libtools: sys-devel/libtool-1.5.2-r7 ACCEPT_KEYWORDS="ppc64 ~ppc64" AUTOCLEAN="yes" CFLAGS="-mcpu=powerpc64 -O2 -fexpensive-optimizations -pipe" CHOST="powerpc64-unknown-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/s hare/config /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/ dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/c onfig/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-mcpu=powerpc64 -O2 -fexpensive-optimizations -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs buildpkg ccache cvs digest sandbox severe strict userpriv u sersandbox" GENTOO_MIRRORS="http://gentoo.osuosl.org http://distro.ibiblio.org/pub/Linux/dis tributions/gentoo" MAKEOPTS="-j 1" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X Xaw3d aalib adns aim alsa altivec apache2 audiofile bash-completion bcmat h berkdb bidi bitmap-fonts bonobo bzlib cdr crypt cscope ctype cups curl curlwra ppers dbm dbx dga dio divx4linux dvd dvdr emacs encode esd ethereal exif f77 fas tcgi fbcon fftw flac flatfile fortran ftp gdbm ggi gif gmp gnome gnutls gphoto2 gpm gtk gtk2 gtkhtml iconv icq imagemagick imap imlib inifile ipv6 jabber jpeg l cms leim lesstiff libgda libwww lirc mad maildir mbox memlimit mhash mikmod mime mitshm mmap mng motif mozilla mpeg mpi msn mule multilib nas ncurses netcdf nls nocardbus offensive ofx oggvorbis opengl oscar oss pam pcntl pcre pdflib perl p hp pic pie plotutils png posix ppc64 python quicktime readline recode sasl sdl s hared sharedmem simplexml slang sndfile sockets ssl svg sysvipc szip tcltk tcpd tetex theora tidy tiff truetype unicode usb wmf xface xine xinerama xml xml2 xml rpc xmms xosd xpm xsl xv xvid yahoo zlib"
Greetings, sys-kernel/ppc64-headers shouldn't be in use anymore. linux26-headers and linux-headers (for 2.4 and 2.6 based headers) is what we've been steering people towards.
Hi, Thanks for the tip... I checked that sys-kernel/linux26-headers merged well on my Imac and is safe from this bug. May this packages be deleted or masked ?
ppc64-headers will be moved to package.mask and then they will be removed in a few weeks.
closing
