Java 7 with emma and junit causing java.lang.VerifyError and Illegal local variable Errors
Asked Answered
I

2

13

So I'm getting these errors

[junit] Illegal local variable table length 17 in method test.nz.ac.massey.cs.sdc.log4jassignment.s06005586.AppenderLayoutTest.()V

[junit] java.lang.VerifyError: Expecting a stackmap frame at branch target 11 in method test.nz.ac.massey.cs.sdc.log4jassignment.s06005586.StressTest.()V at offset 4

[junit] java.lang.ClassFormatError: Illegal local variable table length 17 in method test.nz.ac.massey.cs.sdc.log4jassignment.s06005586.AppenderLayoutTest.()V

And I would like to know how I can fix it...

What I've Read:

What I've Done:

Resources:

For some really crazy reason the JUnit Passes on target="test" but fails on target="emmatest".

This is the output on command prompt from java -version

java version "1.7.0_03"
Java(TM) SE Runtime Environment (build 1.7.0_03-b05)
Java HotSpot(TM) 64-Bit Server VM (build 22.1-b02, mixed mode)

I've tried setting the default arguments for my java7 JRE to -XX:-UseSplitVerifier from here

arguments
(source: iforce.co.nz)

I've also tried to make it complaint with JDK 1.6 on the Project Properties.

complaint
(source: iforce.co.nz)

JUnit direct testing results (no errors on the trace)

junit
(source: iforce.co.nz)

I'm out of options, please help! :(

Ines answered 29/8, 2012 at 8:9 Comment(0)
U
7

Sounds strange.

First, check your code to see if you have used new grammar features introduced in JDK 1.7, like try-with-resource or diamond operator.

I met this VerifyError before, when using cobertura. However, when I set -XX:-UseSplitVerifier to the junit task, it is resolved. I set it by specifying a <jvmarg> nested element to junit task.

Also, most of the coverage libs seem to support JDK1.7 very poorly. However, Jacoco works fine with JDK1.7 so I am using it for now.

Underrate answered 30/8, 2012 at 2:58 Comment(5)
Thanks I managed to fix it, by just downloading the JDK6u25 and changing the library path in my project/eclipse.Ines
@Killrawr Happy to see that! Yes, downgrade the JDK version is also a choice.Underrate
@Killrawr finally you managed to get rid of it by downgrading to java6 as I advised :).Plexiform
@SiB Could you take a look at basic.xml is not in either pmd-bin-5.0-alpha or pmd-bin-5.0.0 directoriesInes
Thanks for the pointer: Cobertura seems to be the root in my case, too.Waistband
G
1

-XX:-UseSplitVerifier

Does work for me and I did not have to downgrade JRE from 1.7 to 1.6

Gramicidin answered 12/2, 2013 at 10:51 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.