You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Vasily Zakharov (JIRA)" <ji...@apache.org> on 2007/07/23 01:22:31 UTC

[jira] Created: (HARMONY-4515) [drlvm] ClassCastException is thrown with low detail

[drlvm] ClassCastException is thrown with low detail
----------------------------------------------------

                 Key: HARMONY-4515
                 URL: https://issues.apache.org/jira/browse/HARMONY-4515
             Project: Harmony
          Issue Type: Bug
          Components: DRLVM
            Reporter: Vasily Zakharov


DRLVM, when throws ClassCastException, provides no detail about what were the class being cast and the target for the cast. This makes localizing problems in applications more difficult.

RI provides information only on the class being cast, and IBM VME provides information on both.

This situation is not certainly a bug, it may be considered an Improvement or Non-bug difference from RI. However I think DRLVM should better follow the IBM VME behavior, or, at least, RI behavior, to improve its usability.

Test to reproduce the problem:

public class Test {
    public static void main(String[] args) {
        try {
            Class c = (Class) (Object) "test";
        } catch (Throwable e) {
            e.printStackTrace();
        }
    }
}

Output on RI:

java.lang.ClassCastException: java.lang.String
        at Test.main(Test.java:4)

Harmony/IBM VME:

java.lang.ClassCastException: java.lang.String incompatible with java.lang.Class
        at Test.main(Test.java:4)

Harmony/DRLVM:

java.lang.ClassCastException
        at Test.main(Test.java:4)


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HARMONY-4515) [drlvm][classloader] ClassCastException is thrown with low detail

Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-4515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gregory Shimansky updated HARMONY-4515:
---------------------------------------

    Assignee: Gregory Shimansky
     Summary: [drlvm][classloader] ClassCastException is thrown with low detail  (was: [drlvm] ClassCastException is thrown with low detail)

> [drlvm][classloader] ClassCastException is thrown with low detail
> -----------------------------------------------------------------
>
>                 Key: HARMONY-4515
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4515
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Vasily Zakharov
>            Assignee: Gregory Shimansky
>         Attachments: H4515.patch, H4515.patch
>
>
> DRLVM, when throws ClassCastException, provides no detail about what were the class being cast and the target for the cast. This makes localizing problems in applications more difficult.
> RI provides information only on the class being cast, and IBM VME provides information on both.
> This situation is not certainly a bug, it may be considered an Improvement or Non-bug difference from RI. However I think DRLVM should better follow the IBM VME behavior, or, at least, RI behavior, to improve its usability.
> Test to reproduce the problem:
> public class Test {
>     public static void main(String[] args) {
>         try {
>             Class c = (Class) (Object) "test";
>         } catch (Throwable e) {
>             e.printStackTrace();
>         }
>     }
> }
> Output on RI:
> java.lang.ClassCastException: java.lang.String
>         at Test.main(Test.java:4)
> Harmony/IBM VME:
> java.lang.ClassCastException: java.lang.String incompatible with java.lang.Class
>         at Test.main(Test.java:4)
> Harmony/DRLVM:
> java.lang.ClassCastException
>         at Test.main(Test.java:4)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HARMONY-4515) [drlvm][jit] ClassCastException is thrown with low detail

Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-4515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gregory Shimansky updated HARMONY-4515:
---------------------------------------

    Priority: Minor  (was: Major)
     Summary: [drlvm][jit] ClassCastException is thrown with low detail  (was: [drlvm][classloader] ClassCastException is thrown with low detail)

Patch for class loader and interpreter is applied at 562267. However when running in JIT mode there is still no details when CCE is thrown. So I am reassigning this bug to JIT to complete the work.

> [drlvm][jit] ClassCastException is thrown with low detail
> ---------------------------------------------------------
>
>                 Key: HARMONY-4515
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4515
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Vasily Zakharov
>            Assignee: Gregory Shimansky
>            Priority: Minor
>         Attachments: H4515.patch, H4515.patch
>
>
> DRLVM, when throws ClassCastException, provides no detail about what were the class being cast and the target for the cast. This makes localizing problems in applications more difficult.
> RI provides information only on the class being cast, and IBM VME provides information on both.
> This situation is not certainly a bug, it may be considered an Improvement or Non-bug difference from RI. However I think DRLVM should better follow the IBM VME behavior, or, at least, RI behavior, to improve its usability.
> Test to reproduce the problem:
> public class Test {
>     public static void main(String[] args) {
>         try {
>             Class c = (Class) (Object) "test";
>         } catch (Throwable e) {
>             e.printStackTrace();
>         }
>     }
> }
> Output on RI:
> java.lang.ClassCastException: java.lang.String
>         at Test.main(Test.java:4)
> Harmony/IBM VME:
> java.lang.ClassCastException: java.lang.String incompatible with java.lang.Class
>         at Test.main(Test.java:4)
> Harmony/DRLVM:
> java.lang.ClassCastException
>         at Test.main(Test.java:4)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HARMONY-4515) [drlvm] ClassCastException is thrown with low detail

Posted by "Pavel Pervov (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-4515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Pervov updated HARMONY-4515:
----------------------------------

    Attachment: H4515.patch

This patch makes DRLVM compatible with Sun in interpreter and Jet lazy mode. Opt mode should be fixed further.

> [drlvm] ClassCastException is thrown with low detail
> ----------------------------------------------------
>
>                 Key: HARMONY-4515
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4515
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Vasily Zakharov
>         Attachments: H4515.patch
>
>
> DRLVM, when throws ClassCastException, provides no detail about what were the class being cast and the target for the cast. This makes localizing problems in applications more difficult.
> RI provides information only on the class being cast, and IBM VME provides information on both.
> This situation is not certainly a bug, it may be considered an Improvement or Non-bug difference from RI. However I think DRLVM should better follow the IBM VME behavior, or, at least, RI behavior, to improve its usability.
> Test to reproduce the problem:
> public class Test {
>     public static void main(String[] args) {
>         try {
>             Class c = (Class) (Object) "test";
>         } catch (Throwable e) {
>             e.printStackTrace();
>         }
>     }
> }
> Output on RI:
> java.lang.ClassCastException: java.lang.String
>         at Test.main(Test.java:4)
> Harmony/IBM VME:
> java.lang.ClassCastException: java.lang.String incompatible with java.lang.Class
>         at Test.main(Test.java:4)
> Harmony/DRLVM:
> java.lang.ClassCastException
>         at Test.main(Test.java:4)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HARMONY-4515) [drlvm] ClassCastException is thrown with low detail

Posted by "Pavel Pervov (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-4515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Pervov updated HARMONY-4515:
----------------------------------

    Attachment: H4515.patch

Attaching correct patch. Previous one was not applying well.

> [drlvm] ClassCastException is thrown with low detail
> ----------------------------------------------------
>
>                 Key: HARMONY-4515
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4515
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Vasily Zakharov
>         Attachments: H4515.patch, H4515.patch
>
>
> DRLVM, when throws ClassCastException, provides no detail about what were the class being cast and the target for the cast. This makes localizing problems in applications more difficult.
> RI provides information only on the class being cast, and IBM VME provides information on both.
> This situation is not certainly a bug, it may be considered an Improvement or Non-bug difference from RI. However I think DRLVM should better follow the IBM VME behavior, or, at least, RI behavior, to improve its usability.
> Test to reproduce the problem:
> public class Test {
>     public static void main(String[] args) {
>         try {
>             Class c = (Class) (Object) "test";
>         } catch (Throwable e) {
>             e.printStackTrace();
>         }
>     }
> }
> Output on RI:
> java.lang.ClassCastException: java.lang.String
>         at Test.main(Test.java:4)
> Harmony/IBM VME:
> java.lang.ClassCastException: java.lang.String incompatible with java.lang.Class
>         at Test.main(Test.java:4)
> Harmony/DRLVM:
> java.lang.ClassCastException
>         at Test.main(Test.java:4)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HARMONY-4515) [drlvm][jit][opt] ClassCastException is thrown with low detail

Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-4515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gregory Shimansky updated HARMONY-4515:
---------------------------------------

    Patch Info:   (was: [Patch Available])
      Assignee:     (was: Gregory Shimansky)
       Summary: [drlvm][jit][opt] ClassCastException is thrown with low detail  (was: [drlvm][jit] ClassCastException is thrown with low detail)

Yes the bug is fixed in all modes except for OPT. So I am reassigning this minor bug to opt.

> [drlvm][jit][opt] ClassCastException is thrown with low detail
> --------------------------------------------------------------
>
>                 Key: HARMONY-4515
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4515
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Vasily Zakharov
>            Priority: Minor
>         Attachments: H4515.patch, H4515.patch
>
>
> DRLVM, when throws ClassCastException, provides no detail about what were the class being cast and the target for the cast. This makes localizing problems in applications more difficult.
> RI provides information only on the class being cast, and IBM VME provides information on both.
> This situation is not certainly a bug, it may be considered an Improvement or Non-bug difference from RI. However I think DRLVM should better follow the IBM VME behavior, or, at least, RI behavior, to improve its usability.
> Test to reproduce the problem:
> public class Test {
>     public static void main(String[] args) {
>         try {
>             Class c = (Class) (Object) "test";
>         } catch (Throwable e) {
>             e.printStackTrace();
>         }
>     }
> }
> Output on RI:
> java.lang.ClassCastException: java.lang.String
>         at Test.main(Test.java:4)
> Harmony/IBM VME:
> java.lang.ClassCastException: java.lang.String incompatible with java.lang.Class
>         at Test.main(Test.java:4)
> Harmony/DRLVM:
> java.lang.ClassCastException
>         at Test.main(Test.java:4)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HARMONY-4515) [drlvm][jit] ClassCastException is thrown with low detail

Posted by "Vasily Zakharov (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HARMONY-4515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517599 ] 

Vasily Zakharov commented on HARMONY-4515:
------------------------------------------

Gregory, the problem seems to be resolved both in Intepreter and JIT mode - it works fine for me on both Windows and Linux.

Could you please double check it in your environment to make sure the problem exists?

Thank you!


> [drlvm][jit] ClassCastException is thrown with low detail
> ---------------------------------------------------------
>
>                 Key: HARMONY-4515
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4515
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Vasily Zakharov
>            Assignee: Gregory Shimansky
>            Priority: Minor
>         Attachments: H4515.patch, H4515.patch
>
>
> DRLVM, when throws ClassCastException, provides no detail about what were the class being cast and the target for the cast. This makes localizing problems in applications more difficult.
> RI provides information only on the class being cast, and IBM VME provides information on both.
> This situation is not certainly a bug, it may be considered an Improvement or Non-bug difference from RI. However I think DRLVM should better follow the IBM VME behavior, or, at least, RI behavior, to improve its usability.
> Test to reproduce the problem:
> public class Test {
>     public static void main(String[] args) {
>         try {
>             Class c = (Class) (Object) "test";
>         } catch (Throwable e) {
>             e.printStackTrace();
>         }
>     }
> }
> Output on RI:
> java.lang.ClassCastException: java.lang.String
>         at Test.main(Test.java:4)
> Harmony/IBM VME:
> java.lang.ClassCastException: java.lang.String incompatible with java.lang.Class
>         at Test.main(Test.java:4)
> Harmony/DRLVM:
> java.lang.ClassCastException
>         at Test.main(Test.java:4)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HARMONY-4515) [drlvm] ClassCastException is thrown with low detail

Posted by "Vasily Zakharov (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HARMONY-4515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514525 ] 

Vasily Zakharov commented on HARMONY-4515:
------------------------------------------

Here's the discussion of this issue on the mailing list:
http://thread.gmane.org/gmane.comp.java.harmony.devel/28387


> [drlvm] ClassCastException is thrown with low detail
> ----------------------------------------------------
>
>                 Key: HARMONY-4515
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4515
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Vasily Zakharov
>
> DRLVM, when throws ClassCastException, provides no detail about what were the class being cast and the target for the cast. This makes localizing problems in applications more difficult.
> RI provides information only on the class being cast, and IBM VME provides information on both.
> This situation is not certainly a bug, it may be considered an Improvement or Non-bug difference from RI. However I think DRLVM should better follow the IBM VME behavior, or, at least, RI behavior, to improve its usability.
> Test to reproduce the problem:
> public class Test {
>     public static void main(String[] args) {
>         try {
>             Class c = (Class) (Object) "test";
>         } catch (Throwable e) {
>             e.printStackTrace();
>         }
>     }
> }
> Output on RI:
> java.lang.ClassCastException: java.lang.String
>         at Test.main(Test.java:4)
> Harmony/IBM VME:
> java.lang.ClassCastException: java.lang.String incompatible with java.lang.Class
>         at Test.main(Test.java:4)
> Harmony/DRLVM:
> java.lang.ClassCastException
>         at Test.main(Test.java:4)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HARMONY-4515) [drlvm] ClassCastException is thrown with low detail

Posted by "Vasily Zakharov (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-4515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vasily Zakharov updated HARMONY-4515:
-------------------------------------

    Patch Info: [Patch Available]

> [drlvm] ClassCastException is thrown with low detail
> ----------------------------------------------------
>
>                 Key: HARMONY-4515
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4515
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Vasily Zakharov
>         Attachments: H4515.patch, H4515.patch
>
>
> DRLVM, when throws ClassCastException, provides no detail about what were the class being cast and the target for the cast. This makes localizing problems in applications more difficult.
> RI provides information only on the class being cast, and IBM VME provides information on both.
> This situation is not certainly a bug, it may be considered an Improvement or Non-bug difference from RI. However I think DRLVM should better follow the IBM VME behavior, or, at least, RI behavior, to improve its usability.
> Test to reproduce the problem:
> public class Test {
>     public static void main(String[] args) {
>         try {
>             Class c = (Class) (Object) "test";
>         } catch (Throwable e) {
>             e.printStackTrace();
>         }
>     }
> }
> Output on RI:
> java.lang.ClassCastException: java.lang.String
>         at Test.main(Test.java:4)
> Harmony/IBM VME:
> java.lang.ClassCastException: java.lang.String incompatible with java.lang.Class
>         at Test.main(Test.java:4)
> Harmony/DRLVM:
> java.lang.ClassCastException
>         at Test.main(Test.java:4)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.