[jboss-jira] [JBoss JIRA] (JASSIST-215) CLONE - "VerifyError: Inconsistent stackmap frames" from PowerMock (using Javassist 3.18.1)

[Laurent GARCIA (JIRA)]

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

Laurent GARCIA updated JASSIST-215:
-----------------------------------

    Description: 
So the new release 3.18.1-GA with powermock is better, but if you have a switch case on an enumeration in the test, the error is still here

{code:java}
Caused by: java.lang.VerifyError: Expecting a stackmap frame at branch target 15 in method foo.bar.MyEnum.myMethod(Ljava/lang/String;)Lfoo/bar/MyEnum; at offset 0
	at foo.bar.MyTest$1.<clinit>(MyTest.java:183)
	at java.lang.Class.forName0(Native Method)
	at java.lang.Class.forName(Class.java:188)
	at org.powermock.modules.agent.PowerMockClassRedefiner.redefine(PowerMockClassRedefiner.java:55)
	at org.powermock.modules.agent.support.PowerMockAgentTestInitializer.redefine(PowerMockAgentTestInitializer.java:49)
	at org.powermock.modules.agent.support.PowerMockAgentTestInitializer.initialize(PowerMockAgentTestInitializer.java:41)
	at org.powermock.modules.testng.PowerMockObjectFactory.newInstance(PowerMockObjectFactory.java:41)
	at org.testng.internal.ClassHelper.createInstance1(ClassHelper.java:387)
	... 22 more
{code}


  was:
So the new release 3.18.1-GA with powermock is better, but if you have a switch case on an enumeration in the test, the error is still here



    
> CLONE - "VerifyError: Inconsistent stackmap frames" from PowerMock (using Javassist 3.18.1)
> -------------------------------------------------------------------------------------------
>
>                 Key: JASSIST-215
>                 URL: https://issues.jboss.org/browse/JASSIST-215
>             Project: Javassist
>          Issue Type: Bug
>    Affects Versions: 3.18.1-GA
>         Environment: jdk1.7.0_25
>            Reporter: Laurent GARCIA
>            Assignee: Shigeru Chiba
>
> So the new release 3.18.1-GA with powermock is better, but if you have a switch case on an enumeration in the test, the error is still here
> {code:java}
> Caused by: java.lang.VerifyError: Expecting a stackmap frame at branch target 15 in method foo.bar.MyEnum.myMethod(Ljava/lang/String;)Lfoo/bar/MyEnum; at offset 0
> 	at foo.bar.MyTest$1.<clinit>(MyTest.java:183)
> 	at java.lang.Class.forName0(Native Method)
> 	at java.lang.Class.forName(Class.java:188)
> 	at org.powermock.modules.agent.PowerMockClassRedefiner.redefine(PowerMockClassRedefiner.java:55)
> 	at org.powermock.modules.agent.support.PowerMockAgentTestInitializer.redefine(PowerMockAgentTestInitializer.java:49)
> 	at org.powermock.modules.agent.support.PowerMockAgentTestInitializer.initialize(PowerMockAgentTestInitializer.java:41)
> 	at org.powermock.modules.testng.PowerMockObjectFactory.newInstance(PowerMockObjectFactory.java:41)
> 	at org.testng.internal.ClassHelper.createInstance1(ClassHelper.java:387)
> 	... 22 more
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira