public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Anthony Green <green@build.tokyo.redhat.com> To: gcc-gnats@gcc.gnu.org Subject: java/8415: reflection bug: exception info for Method Date: Thu, 31 Oct 2002 09:26:00 -0000 [thread overview] Message-ID: <200210311728.g9VHSw1T000458@build.tokyo.redhat.com> (raw) >Number: 8415 >Category: java >Synopsis: reflection bug: exception info for Method >Confidential: no >Severity: critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu Oct 31 09:26:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Anthony Green >Release: 3.3 20021031 (experimental) >Organization: >Environment: System: Linux build.tokyo.redhat.com 2.4.18-14smp #1 SMP Wed Sep 4 12:34:47 EDT 2002 i686 i686 i386 GNU/Linux Architecture: i686 host: i686-pc-linux-gnu build: i686-pc-linux-gnu target: i686-pc-linux-gnu configured with: ../../FSF/GCC/HEAD/gcc/configure --prefix=/home/green/latest/i --enable-threads --enable-languages=c,c++,java : (reconfigured) >Description: libgcj doesn't build proper reflection data for interpreted classes. The problem is that the format of the names of the exception classes differs between native and interpreted code. For native code we get "LMyException;", and for interpreted code we get "MyException". libgcj is written to expect "LMyException;". What you end up with in Method is a Class[] filled with null instead of a proper array of exception classes. >How-To-Repeat: I don't have a simple test case prepared. However, all you need to do to trigger this is call Method.toString() on a Method of an interpreted class which throws an exception. >Fix: This work-around seems useful for now. Another fix would be to change the format of the meta-data emitted by the compiler. Index: java/lang/reflect/natMethod.cc =================================================================== RCS file: /cvs/gcc/gcc/libjava/java/lang/reflect/natMethod.cc,v retrieving revision 1.29 diff -2 -c -p -r1.29 natMethod.cc *** java/lang/reflect/natMethod.cc 27 Aug 2002 23:57:17 -0000 1.29 --- java/lang/reflect/natMethod.cc 31 Oct 2002 17:16:00 -0000 *************** java::lang::reflect::Method::getType () *** 208,213 **** jclass *elts = elements (exception_types); for (int i = 0; i < count; ++i) ! elts[i] = _Jv_FindClassFromSignature (method->throws[i]->data, ! declaringClass->getClassLoader ()); } --- 208,228 ---- jclass *elts = elements (exception_types); for (int i = 0; i < count; ++i) ! { ! char *c = (char *) method->throws[i]->data; ! int len = strlen (c); ! if (c[0] != 'L' && c[len-1] != ';') ! { ! char name[len+3]; ! name[0] = 'L'; ! strcpy (&name[1], c); ! name[len+1] = ';'; ! name[len+2] = 0; ! elts[i] = _Jv_FindClassFromSignature (name, ! declaringClass->getClassLoader ()); ! } ! else ! elts[i] = _Jv_FindClassFromSignature (method->throws[i]->data, ! declaringClass->getClassLoader ()); ! } } >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-10-31 17:26 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-31 9:26 Anthony Green [this message] 2002-11-01 12:56 Tom Tromey 2002-11-02 13:34 tromey
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=200210311728.g9VHSw1T000458@build.tokyo.redhat.com \ --to=green@build.tokyo.redhat.com \ --cc=gcc-gnats@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).