Closed graymalkin closed 9 years ago
Hmm, the gdb output is suspect - perhaps this is an issue with this particular machine, rather than AXE.
warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
Program received signal SIGSEGV, Segmentation fault.
warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
?? (warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
) at /scratch/richard/gcc-build/32bit/i686-pc-linux-gnu/libstdc++-v3/include/sstream:60
60 /scratch/richard/gcc-build/32bit/i686-pc-linux-gnu/libstdc++-v3/include/sstream: No such file or directory.
in /scratch/richard/gcc-build/32bit/i686-pc-linux-gnu/libstdc++-v3/include/sstream
warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
:/ This is still failing on the 32 bit Centos build bot. I don't know if this is platform agnostic or not.
The Centos machine has an
Intel(R) Xeon(R) CPU X3363 @ 2.83GHz
CPU.It is passing on my 32 bit VMs (Ubuntu 14.04 and Windows 7 sp1)
I've not checked if it's failing in exactly the same way yet, but it's certainly the same sort of place. The test is in
test/fibonacci.c
.Bad News, Everyone!