internal compiler error?
Steve Kargl
sgk at troutmask.apl.washington.edu
Sun Mar 14 13:37:59 PST 2004
Anyone else see problems with collect2?
kargl[203] gcc -o h h.c
gcc: Internal error: Bad system call (program collect2)
Please submit a full bug report.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
kargl[204] cat h.c
#include <stdio.h>
int main(void) {
printf("Hello world.\n");
return 0;
}
kargl[204] truss gcc -o h h.c
stat("/usr/libexec/collect2",0xbfbfe630) = 0 (0x0)
access("/usr/libexec/collect2",1) = 0 (0x0)
fork() = 938 (0x3aa)
SIGNAL 20
wait4(0xffffffff,0xbfbfe73c,0x0,0x0) = 938 (0x3aa)
gcc: write(2,0xbfbfdfd0,5) = 5 (0x5)
Internal error: Bad system call (program collect2)
Please submit a full bug report.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.write(2,0xbfbfdff0,140) = 140 (0x8c)
write(2,0x806d4f3,1) = 1 (0x1)
stat("/var/tmp/cc7im6mN.o",0xbfbfe630) = 0 (0x0)
unlink("/var/tmp/cc7im6mN.o") = 0 (0x0)
stat("/var/tmp/cc2Mhzku.s",0xbfbfe630) = 0 (0x0)
unlink("/var/tmp/cc2Mhzku.s") = 0 (0x0)
exit(0x1)
process exit, rval = 256
Could this be caused by the Intel C/C++ compiler commits or the
recent commits by Peter to push gaint down into fork?
--
Steve
More information about the freebsd-current
mailing list