harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Fursov (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, 12 Sep 2007 11:56:32 GMT

    [ https://issues.apache.org/jira/browse/HARMONY-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526753
] 

Mikhail Fursov commented on HARMONY-1945:
-----------------------------------------

SM and CL tests passes after lazy resolution was enabled in all modes.


test1.zip fails in both JET and OPT modes:

Harmony:

C:\users\mfursov\tests\resolve\intf>C:\users\mfursov\harmony\drlvm_test\build\win_ia32_msvc_release\deploy\jdk\jre\bin\java.exe
-Xem:op
t -XX:jit.arg.lazyResolution=on  test1
Expected: java.lang.NoClassDefFoundError: test1_1
    test1.main(test1.java:10)
new test_1: null
Test failed: Unexpected exception on method invocation java.lang.NullPointerException
java.lang.NullPointerException
        at test1.main(test1.java:24)




RI:

C:\users\mfursov\tests\resolve\intf>java test1
Expected: java.lang.NoClassDefFoundError: test1_1
    test1.main(test1.java:10)
new test_1: null
Expected: java.lang.NoClassDefFoundError: test1_1
    test1.main(test1.java:24)
Test passed



Reason: we must check if class is found for all lazy resolution helpers before NULL checks.
It requires changes in both OPT and JET compilers (avoid NULL checks generation for lazy helpers)

> [drlvm][jit] The "fake" circularity errors and wrong line numbers.in class loader exceptions.
> ---------------------------------------------------------------------------------------------
>
>                 Key: HARMONY-1945
>                 URL: https://issues.apache.org/jira/browse/HARMONY-1945
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Pavel Afremov
>            Assignee: Mikhail Fursov
>         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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message