Hi, I filed PR61538 about two weeks ago, regarding gcc-4.8.x and up not compiling a g++/pthreads-linked app correctly on SGI R1x000-based systems (Octane, Onyx2), running Linux. Running the subsequently-compiled application simply hangs in a futex syscall until terminated via Ctrl+C. I suspect it's a double-locking bug of some design, as evidenced by strace showing two consecutive syscall()'s w/ 0x108e passed as the syscall # (4238 or futex on o32 MIPS), but I am stumped as to what else I can do to debug it and help fix it.
I haven't fully determined if the flaw originates in gcc, glibc, or even the kernel. I picked gcc for now because gcc-4.7.x and earlier do not exhibit the problem. So for now, I am stuck on using gcc-4.7.x on these systems until the problem is located and fixed. Full details: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61538 Thanks!, -- Joshua Kinard Gentoo/MIPS ku...@gentoo.org 4096R/D25D95E3 2011-03-28 "The past tempts us, the present confuses us, the future frightens us. And our lives slip away, moment by moment, lost in that vast, terrible in-between." --Emperor Turhan, Centauri Republic
