From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31833 invoked by alias); 16 Dec 2005 01:01:21 -0000 Received: (qmail 31810 invoked by uid 48); 16 Dec 2005 01:01:21 -0000 Date: Fri, 16 Dec 2005 01:01:00 -0000 Message-ID: <20051216010121.31809.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug java/24698] [4.1/4.2 regression] SIGABRT when trying to read properties files from jars; and CLASSPATH . no longer implied for class specified on the command line In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: java-prs@gcc.gnu.org From: "bero at arklinux dot org" Mailing-List: contact java-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-prs-owner@gcc.gnu.org X-SW-Source: 2005-q4/txt/msg00521.txt.bz2 List-Id: ------- 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