On Mon, 2005-10-31 at 13:27 -0600, Rich Adamson wrote: > fc3, current cvs-head from 1:25pm today... > > make[1]: Leaving directory `/usr/src/asterisk/stdtime' > gcc -pipe -Wall -Wstrict-prototypes -Wmissing-prototypes > -Wmissing-declaration > s -g -Iinclude -I../include -D_REENTRANT -D_GNU_SOURCE -O6 -march=i686 > -DZAPTE > L_OPTIMIZATIONS -fomit-frame-pointer -c -o io.o io.c > gcc -pipe -Wall -Wstrict-prototypes -Wmissing-prototypes > -Wmissing-declaration > s -g -Iinclude -I../include -D_REENTRANT -D_GNU_SOURCE -O6 -march=i686 > -DZAPTE > L_OPTIMIZATIONS -fomit-frame-pointer -c -o sched.o sched.c > gcc -pipe -Wall -Wstrict-prototypes -Wmissing-prototypes > -Wmissing-declaration > s -g -Iinclude -I../include -D_REENTRANT -D_GNU_SOURCE -O6 -march=i686 > -DZAPTE > L_OPTIMIZATIONS -fomit-frame-pointer -c -o logger.o logger.c > logger.c: In function `ast_queue_log': > logger.c:369: internal compiler error: Segmentation fault > Please submit a full bug report, > with preprocessed source if appropriate. > See <URL:http://bugzilla.redhat.com/bugzilla> for instructions. > The bug is not reproducible, so it is likely a hardware or OS problem. > gcc: Internal error: Segmentation fault (program as) > Please submit a full bug report. > See <URL:http://bugzilla.redhat.com/bugzilla> for instructions. > make: *** [logger.o] Error 1
Under normal situations, gcc should not segfault. GCC segfaulting is usually a sign that you are using either a not well tested version of gcc, or you have memory errors that allow gcc to segfault. I don't doubt there are other ways of killing gcc, but it isn't the norm. -- Steven Critchfield <[EMAIL PROTECTED]> _______________________________________________ Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev