harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Afremov (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-1945) [drlvm][jit] The "fake" circularity errors and wrong line numbers.in class loader exceptions.
Date Wed, 13 Dec 2006 11:36:26 GMT
    [ http://issues.apache.org/jira/browse/HARMONY-1945?page=comments#action_12458085 ] 
Pavel Afremov commented on HARMONY-1945:

The bug, which test from test.zip shows, consist from 2 parts.
1)      First Class Loading now happens during method compilation. By this
reason NoClassDefFoundError has incorrect stack trace, i.e. the stack for the
place when compilation is started.
2)      The second issue that ClassLoader saves loading error, and throws it
when the classes loaded again. By this reason exception stack is the same as
for first time as for second time.

The second part can depends on Harmony-2083.

> [drlvm][jit] The "fake" circularity errors and wrong line numbers.in class loader exceptions.
> ---------------------------------------------------------------------------------------------
>                 Key: HARMONY-1945
>                 URL: http://issues.apache.org/jira/browse/HARMONY-1945
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Pavel Afremov
>         Attachments: CLTest.java, SMTest.java, test1.zip
> There are two bugs which have one source - unimplemented lazy class resolution.
> One bug is fake circularity errors in some cases, the other is wrong line numbers in
exception which generated during  class resolution. 
> To show "fake circularity error" there are two "impossible" tests. One test is more simple
and use SecurityManager. The other is a bit more complex and uses custom ClassLoader. You
can find them in attachment. 
> To show wrong line number in class loader exceptions use the third test.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message