You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@harmony.apache.org by "Pavel Afremov (JIRA)" <ji...@apache.org> on 2006/12/13 12:26:23 UTC

[jira] Updated: (HARMONY-1945) [drlvm][jit] The "fake" circularity errors and wrong line numbers.in class loader exceptions.

     [ http://issues.apache.org/jira/browse/HARMONY-1945?page=all ]

Pavel Afremov updated HARMONY-1945:
-----------------------------------

        Summary: [drlvm][jit] The "fake" circularity errors and wrong line numbers.in class loader exceptions.  (was: [drlvm][test] The "fake" circularity errors)
     Issue Type: Bug  (was: Test)
    Description: 
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.


  was:
There are two "impossible" tests, which shows "fake" circularity errors. 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. 


       Priority: Major  (was: Minor)

> [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