public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "mckinlay at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug libgcj/17021] New: gij: class resolution throws errors too eagerly Date: Fri, 13 Aug 2004 21:07:00 -0000 [thread overview] Message-ID: <20040813210724.17021.mckinlay@redhat.com> (raw) NoClassDefFoundError should only be thrown if a code path that attempts to use the missing class is actually used. GIJ, however, throws the error too early. This can be seen by compiling the following test case and deleting the class file for "Bar". $ gcj -C Foo.java Bar.java $ rm Bar.class $ gij Foo Exception in thread "main" java.lang.NoClassDefFoundError: while resolving class: Foo at java.lang.ClassLoader.resolveClass0(java.lang.Class) (/usr/lib/libgcj.so.4.0.0) at java.lang.Class.initializeClass() (/usr/lib/libgcj.so.4.0.0) at java.lang.Class.forName(java.lang.String, boolean, java.lang.ClassLoader) (/usr/lib/libgcj.so.4.0.0) ... public class Foo { public boolean missing_class_code_path = false; public static void main(String[] args) { new Foo().j(); } void j() { if (missing_class_code_path) new Bar().x(); } } public class Bar { public void x() {} } -- Summary: gij: class resolution throws errors too eagerly Product: gcc Version: 3.5.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: libgcj AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mckinlay at redhat dot com CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17021
next reply other threads:[~2004-08-13 21:07 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-08-13 21:07 mckinlay at redhat dot com [this message] 2004-08-13 21:51 ` [Bug libgcj/17021] " pinskia at gcc dot gnu dot org 2004-10-13 21:33 ` tromey at gcc dot gnu dot org 2005-07-13 18:12 ` pinskia at gcc dot gnu dot org 2005-07-13 21:43 ` [Bug libgcj/17021] gij: class resolution throws errors too eagerl dberlin at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20040813210724.17021.mckinlay@redhat.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-prs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).