------- Comment #11 from bero at arklinux dot org 2005-12-16 01:01 ------- After adding some debug statements, I can add that the SIGABRT happens in org.eclipse.jdt.internal.compiler.parser.Parser's readReadableNameTable method.
ResourceBundle.getBundle() succeeds [doesn't throw a MissingResourceException, which is odd because strace clearly shows it looking in the wrong place (.class instead of .properties), but maybe the bundle is indeed found after accessing a nonexistant class file (maybe the lookup order should be changed?)]. A couple of lines later, the line "String n = bundle.getString(name[i]);" triggers the SIGABRT. The code doesn't get past the line, and doesn't enter the MissingResourceException handler either. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24698
