------- Comment #10 from aph at gcc dot gnu dot org 2008-06-14 06:27 ------- The only way I can find out which file in libgcj causes the stack overflow is to try to build it again with an unoptimized gcc. I can do so next week.
-- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36218
