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 Rebriy (JIRA)" <ji...@apache.org> on 2007/03/01 11:46:50 UTC
[jira] Updated: (HARMONY-3270) [drlvm][verifier] verifier rejects
correct method
[ https://issues.apache.org/jira/browse/HARMONY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Rebriy updated HARMONY-3270:
----------------------------------
Attachment: verifier_return_check_fix.patch
The bug was in data flow analysis for return instruction.
The patch is correcting the issue.
> [drlvm][verifier] verifier rejects correct method
> ---------------------------------------------------
>
> Key: HARMONY-3270
> URL: https://issues.apache.org/jira/browse/HARMONY-3270
> Project: Harmony
> Issue Type: Sub-task
> Components: DRLVM
> Environment: all
> Reporter: Vera Volynets
> Attachments: verifier_return_check_fix.patch
>
>
> I tried to reproduce test case from Harmony-2558, but it failed because of VerifyError exception.
> The output:
> java.lang.VerifyError: (class: Jasm_part, method: do_new_without_invokespecial()V) Wrong return type in function
> But the method is correct:
> Method name:"do_new_without_invokespecial" static Signature: 9=()void
> Attribute "Code", length:16, max_stack:1, max_locals:1, code_length:4
> 0: new #1=<Class Broken_clinit>
> 3: return
> Return type is void.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.