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] [Updated] (BCEL-183) JustIce verifier checks for field and variable name validity whereas it is not needed
Date Wed, 17 Dec 2014 09:12:13 GMT

     [ https://issues.apache.org/jira/browse/BCEL-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jérôme Leroux updated BCEL-183:
-------------------------------
    Attachment: BCEL-183-2.zip
                BCEL-183-2.patch

Actually, these issues in the JustIce verifier was due to lack of documentation in the Second
Edition of _The Java Virtual Machine Specification_.
The  Java SE 7 Edition of _The Java Virtual Machine Specification_ incorporates some clarifications
about this subject (see section 4.2.2).
I attach a new patch that replaces the previous one and the associated test classfiles.

> JustIce verifier checks for field and variable name validity whereas it is not needed
> -------------------------------------------------------------------------------------
>
>                 Key: BCEL-183
>                 URL: https://issues.apache.org/jira/browse/BCEL-183
>             Project: Commons BCEL
>          Issue Type: Bug
>          Components: Verifier
>    Affects Versions: 5.2, 6.0
>            Reporter: Jérôme Leroux
>         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