harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Astapchuk (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-1769) [drlvm][jvmti] Unexpected exception in JVMTI mode
Date Tue, 31 Oct 2006 11:23:19 GMT
    [ http://issues.apache.org/jira/browse/HARMONY-1769?page=comments#action_12445873 ] 
Alex Astapchuk commented on HARMONY-1769:

Sorry for the late replay. Here are answers:

> why does it need eclipse compiler?
The test to reproduce the bug must be compiled by Eclipse compiler. 
As Gregory correctly said, the Eclipse compiler produces the code using SWAP opcode.
The Sun's javac lives w/o the SWAP in this case.

> Still I wonder how adding a new function which isn't apparently used anywhere 
> in the patch solves the problem.

The added function specify some overloaded things to be more precise.
The problem was exactly that wrong overloaded method was called.
It also prevents from similar troubles in the future.

> [drlvm][jvmti] Unexpected exception in JVMTI mode
> -------------------------------------------------
>                 Key: HARMONY-1769
>                 URL: http://issues.apache.org/jira/browse/HARMONY-1769
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Alex Astapchuk
>         Assigned To: Geir Magnusson Jr
>         Attachments: harmony-1769-jvmti-jet-swap-bug.patch, JetSwapBug.class, JetSwapBug.java
> The attached test throws unxepected ArrayIndexOutOfBoundsException when executed under
> The problem is incorrect processing of SWAP opcode in Jitrino.JET.
> NOTE: Please use either attached class-file to reproduce, or compile with Eclipse's compiler.
> How to reproduce: run under JVMTI mode on:
>  java -Xem:jet -Dvm.jvmti.enabled=true JetSwapBug
>  If you see 'Test passed', then the test indeed passes.
>  If the bug still exists, you'll see ArrayIndexOutOfBoundsException.

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