------- Comment #6 from rob1weld at aol dot com 2009-01-17 14:32 ------- Created an attachment (id=17126) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17126&action=view) Screenshot of build shows libgcj_tools crashing (hogging memory)
Here we have a screenshot of gcc building 'libgcj_tools' (the two humps) and crashing on the second one. The next attachment (a reboot was necessary to continue the build) shows that the second hump completes and the build finished shortly thereafter. I configured gcc using: # gcc/xgcc -v Using built-in specs. Target: i386-pc-solaris2.11 Configured with: ../gcc_trunk/configure --enable-languages=ada,c,c++,fortran,java,objc,obj-c++ --enable-shared --disable-static --enable-decimal-float --with-long-double-128 --enable-nls --with-included-gettext --enable-gather-detailed-mem-stats --with-stabs --enable-debug --enable-largefile --enable-symvers --without-system-zlib --enable-gtk-cairo --enable-gconf-peer --enable-xmlj --enable-gtk-peer --enable-qt-peer --enable-plugin --enable-tool-wrappers --enable-local-sockets --enable-gjdoc --enable-java-awt=gtk,xlib,qt,x --enable-gc-debug --enable-libgcj-debug --enable-objc-gc --enable-libstdcxx-debug --disable-stage1-checking --enable-checking=release --without-system-libunwind --with-gnu-as --with-as=/usr/local/bin/as --with-gnu-ld --with-ld=/usr/local/bin/ld Thread model: posix gcc version 4.4.0 20090117 (experimental) [trunk revision 143454] (GCC) It does matter which options you use since I had 'little trouble' a week ago with few additional ./configure options and 'some trouble' with a few more options added. Now that I've added all these extra options I am at a point where gcc will barely compile with all my available memory. Rob -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38717
