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-3079) [dlrvm][classloader][opt] Opt does not handle exception raised by classloader (assertion fails classloader.cpp:1521)
Date Tue, 13 Feb 2007 12:59:05 GMT

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

Mikhail Fursov commented on HARMONY-3079:
-----------------------------------------

Here is one more minitest to show that JIT does not handle unresolved types correctly. (Minimized
eclipse bug version)

1) Compile
2) Remove A1,A2 classes
3) Run

public class Test {


    public static void main(String args[]) {
        foo1();
        foo2();
        System.out.println("PASSED!");
    }
    static A1 foo1(){return null;}
    static A2 foo2(){return null;}

}
class A1 {}
class A2 {}

> [dlrvm][classloader][opt] Opt does not handle exception raised by classloader (assertion
fails classloader.cpp:1521)
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: HARMONY-3079
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3079
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: Win IA32, OPT
>            Reporter: Aleksey Ignatenko
>         Attachments: H3079.patch, test.zip
>
>
> Assertion failed - classloader.cpp:1521 on EUT jdtdebug suit. 
> Testcase:2 methods return the same type, 1-st method calls the 2-nd:
> class A;
> class B{
> static A getA(){return new A();}}
> class C{
> static A getA(){return B.getA();}}
> main: C.getA();
> JIT tries to resolve A class 2 times. If class is not accessable, classloader raises
ClassNotfoundException 1-st time, JIT does not handle it, then when the 2-nd time JIT tries
to resolve the same class VM fails with the assert on loading (because exception was already
raised). 
> The issue here is that  JIT does not handle raised exception by classloader in 1 compilation
session.

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