[jboss-jira] [JBoss JIRA] (JASSIST-145) erroneous "bad array type for AALOAD: null" when verifying

Shigeru Chiba (Resolved) (JIRA) jira-events at lists.jboss.org
Wed Oct 19 01:03:45 EDT 2011


     [ https://issues.jboss.org/browse/JASSIST-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shigeru Chiba resolved JASSIST-145.
-----------------------------------

    Fix Version/s: 3.16.0-GA
       Resolution: Done


fixed as Johannes suggested.
                
> erroneous "bad array type for AALOAD: null" when verifying
> ----------------------------------------------------------
>
>                 Key: JASSIST-145
>                 URL: https://issues.jboss.org/browse/JASSIST-145
>             Project: Javassist
>          Issue Type: Bug
>    Affects Versions: 3.15.0-GA
>            Reporter: Shigeru Chiba
>            Assignee: Shigeru Chiba
>             Fix For: 3.16.0-GA
>
>
> (reported by Johannes Schindelin)
> When verifying bytecode compiled for Java 1.6+ where we need to provide a
> StackMapTable attribute which we verify ourselves first, the sequence
> 	ACONST_NULL
> 	ASTORE_0
> 	...
> 	ALOAD_0
> 	ICONST_0
> 	AALOAD
> triggers the verifier to add NullType as an equivalent type for the
> ArrayType. Since that code might be unreachable after instrumenting or the
> local variable might have been set otherwise before jumping back to this
> code, we really need ArrayType's isNullType() method to report the correct
> result.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-jira mailing list