[jboss-jira] [JBoss JIRA] (JASSIST-268) Gettig Java.lang.VerifyError with Latest Javassist, Powermock 1.7 and Java 1.8

Pedro Cerejo (JIRA) issues at jboss.org
Tue Apr 24 10:04:00 EDT 2018


    [ https://issues.jboss.org/browse/JASSIST-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566185#comment-13566185 ] 

Pedro Cerejo edited comment on JASSIST-268 at 4/24/18 10:03 AM:
----------------------------------------------------------------

I'm also encountering the same error. In my case the error appears when i use the appendBefore method, with a for that has a continue, like a simple for:
{code:java}
for(int i = 0; i < beforeMethods.length; i++) {
     continue;
}
{code}

for methods *with more than one argument*. 
I'm assuming that has something to do with labels but i know nothing about bytecode so don't quote me on that.


was (Author: schimini):
I'm also encountering the same error. In my case the error appears when i use the appendBefore method, with a for that has a continue, like a simple for:
{code:java}
for(int i = 0; i < beforeMethods.length; i++) {
     continue;
}
{code}

for methods with more than one argument. 
I'm assuming that has something to do with labels but i know nothing about bytecode so don't quote me on that.

> Gettig Java.lang.VerifyError with Latest Javassist, Powermock 1.7 and Java 1.8
> ------------------------------------------------------------------------------
>
>                 Key: JASSIST-268
>                 URL: https://issues.jboss.org/browse/JASSIST-268
>             Project: Javassist
>          Issue Type: Bug
>    Affects Versions: 3.20.0-GA
>         Environment: All
>            Reporter: Rajesh Eagambaram
>            Assignee: Shigeru Chiba
>
> Hi Team,
> We have our current JUnit development completed using Java 1.6 using Powermock1.7 and Javaassist 3.20.0-GA and it is working fine. When we upgrade the JDK to 1.8 we are getting the error "Java.lang.VerifyError: Expecting a stackmap frame at branch target 64".
> Please help to fix the issue



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)


More information about the jboss-jira mailing list