On 12/20/05, Bruce Dubbs <[EMAIL PROTECTED]> wrote: > ServerBeach replaced the system memory on anduin last night. I compiled > gcc-4.02 to test it out, but I got a segfault at exactly the same place > it did before. > > Upon analysis, it looks like the first invocation of stage1/xgcc fails.
This isn't necessarily true. I still think it's a system issue that doesn't have to do with gcc. > stage1/xgcc -Bstage1/ -B/tools/i686-pc-linux-gnu/bin/ -O2 -g > -fomit-frame-pointer -DIN_GCC -W -Wall -Wwrite-strings > -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long > -Wno-variadic-macros -Wold-style-definition -DHAVE_CONFIG_H -I. -I. > -I../../gcc-4.0.2/gcc -I../../gcc-4.0.2/gcc/. > -I../../gcc-4.0.2/gcc/../include -I../../gcc-4.0.2/gcc/../libcpp/include > -c insn-attrtab.c -o insn-attrtab.o --verbose I just got past this spot, but watched top while this command was running. It pushed the memory within 20000K of full and started to use the swap a bit. I think this command is just really stressing the resources and triggering a system issue. In fact googling "insn-attrtab segfault" give this result which shows that insn-attrtab compile uses a lot of memory: http://gcc.gnu.org/ml/gcc-regression/2004-10/msg00110.html Also found a long thread on the Gentoo forums. Apparently, this isn't the only time this has occurred. Most of the people are amd64, but one person has athlon xp. What board is this on? A bunch of people there had DFI boards. Here's the link http://forums.gentoo.org/viewtopic-t-358266.html > and it completed successfully! As I said yesterday, the errors haven't been consistent for me. Sometimes it completes this step successfully, sometimes it segfaults during stage2 during the same compile command, sometimes it bombs at other spots, once I got something like glibc: malloc() Memory corruption detected! I hope someone knows how to analyze this, but I still doubt that there are not hardware issues. And now I got through gcc, so there's another data point on the randomness of this segfaulting. We might have to run this through a debugger if it keeps happening, though. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
