------- Comment #4 from rmathew at gcc dot gnu dot org 2006-03-29 10:06 ------- It would be difficult for those of us without alpha-linux boxes to track this problem down. If you're willing, you can try to track the failure to a certain bit yourself.
Let's stick with the GCC 4.2 snapshot as that's the latest and is likely to already contain many useful fixes. Looking at your build log, try to reproduce the failure yourself on the command line. That is, copy-paste the command-line compiling "gnuRuntime.java" and run it with your working directory set to the $BUILD_DIR/$TARGET/libjava folder, where $BUILD_DIR is the folder in which you are building GCC and $TARGET is the target you're building for (alpha-alphaslack-linux). Once you're able to reproduce this failure on the command-line, get a recent version of GDB and get the "debugx" and "debug" scripts from: http://gcc.gnu.org/ml/gcc/2004-03/msg01195.html Now run "debugx jc1 <rest-of-command-line>", where "<rest-of-command-line>" was the entire command noted earlier that causes the failure. Within GDB, type "run" and when the segmentation fault occurs, type "list" and then "backtrace". This should give some useful information. More information can be found here: http://gcc.gnu.org/wiki/DebuggingGCC Good luck! -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26879
