commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jérôme Leroux (JIRA) <j...@apache.org>
Subject [jira] [Commented] (BCEL-183) Implement Java 7 field/method name validation rules
Date Tue, 10 Mar 2015 08:28:38 GMT

    [ https://issues.apache.org/jira/browse/BCEL-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14354534#comment-14354534
] 

Jérôme Leroux commented on BCEL-183:
------------------------------------

As mentionned before, the patch seems to be valid for the classfiles from the version 51 only.
Currently the verifier does not rely on the classfile version to adapt the verification. The
verifier is compliant with the second edition of the _Java Virtual Machine specification_
but does not manage all the new features added by the _Java SE 7_ edition.
Actually, I don't know if the verifier should rely on the version of the classfile. The version
of the targeted virtual machine may be specified with an option.

> Implement Java 7 field/method name validation rules
> ---------------------------------------------------
>
>                 Key: BCEL-183
>                 URL: https://issues.apache.org/jira/browse/BCEL-183
>             Project: Commons BCEL
>          Issue Type: Improvement
>          Components: Verifier
>    Affects Versions: 5.2
>            Reporter: Jérôme Leroux
>             Fix For: 6.0
>
>         Attachments: BCEL-183-2.patch, BCEL-183-2.zip, BCEL-183-src.zip, BCEL-183.patch,
BCEL-183.zip
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> The JustIce bytecode verifier checks the validity of the field name and the variable
name considering the java langage specification. 
> This check is not specified by the bytecode verifier specification.
> This may lead to bytecode verification errors in pass2 on valid classfiles.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message