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 Mon, 15 Dec 2014 16:41: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-src.zip

The previously attached classfiles have not been directly generated from the source files.
Here is the source files. To get the test classfiles, the classfiles generated from these
sources must be modified. 
The modification consists in modifying the fields and variables names in the constant pool.
I prefixed all these names with the character '0'. 
For example, the name {{0field}} is not a valid Java identifier for the Java langage but it
is valid for the Java virtual machine.

> 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-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