使用 Proguard 对逻辑操作进行 VerifyError

Question

我在 android 库上使用 Proguard，但它似乎在一个特定的 class 上创建了一个 VerifyError，同时收缩或混淆示例代码。（即使用 -dontobfuscate 和 -dontshrink 将消除错误）。

我可以用一个简单的例子找出 GitHub repository 上的错误（命令 ./gradlew clean test 应该重现错误）但我真的不明白这里的真正问题。

我失败的测试只会尝试实例化一个对象：

package a.b.c;

public class FailingTest {
  @org.junit.Test
  public void name() throws Exception {
    new D();
  }
}

关联的class就这么简单：

package a.b.c;

public class D {
  public void f(int g) {
    if (g < 0) {
      System.out.println("test");
    }
  }
}

事实上，任何逻辑操作都会引发错误（例如，仅将 System.out.println(g == 2); 放入方法体中也会失败）。

Proguard配置如下：

-keep public class a.b.c.D {
    public protected *;
}

# With those options, the test will be successful.
#-dontobfuscate
#-dontshrink

堆栈跟踪如下：

java.lang.VerifyError: Expecting a stackmap frame at branch target 37
Exception Details:
  Location:
    a/b/c/D.f(I)V @17: ifeq
  Reason:
    Expected stackmap frame at this location.
  Bytecode:
    0x0000000: bb00 0559 b700 0ab6 000b 4d2c b900 0c01
    0x0000010: 0099 0014 2cb9 000d 0100 4eb2 0007 2db6
    0x0000020: 0008 a7ff e9b1                         

    at a.b.c.FailingTest.name(FailingTest.java:7)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:497)
    at org.junit.runners.model.FrameworkMethod.runReflectiveCall(FrameworkMethod.java:50)
    at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
    at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
    at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
    at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
    at org.junit.runners.ParentRunner.run(ParentRunner.java:290)
    at org.junit.runners.ParentRunner.schedule(ParentRunner.java:71)
    at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
    at org.junit.runners.ParentRunner.access[=13=]0(ParentRunner.java:58)
    at org.junit.runners.ParentRunner.evaluate(ParentRunner.java:268)
    at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
    at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
    at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
    at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
    at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:497)
    at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
    at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
    at org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
    at org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
    at com.sun.proxy.$Proxy3.processTestClass(Unknown Source)
    at org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:497)
    at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
    at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
    at org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:377)
    at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
    at org.gradle.internal.concurrent.StoppableExecutorImpl.run(StoppableExecutorImpl.java:40)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)

Answer 1

正在将构建脚本的依赖项 com.android.tools.build:gradle 从 2.3.3 更新为 3.0.0 和 gradle wrapper 从 3.3 到 4.1 似乎修复了 Proguard 的行为。

我猜这是嵌入在这个特定依赖项中的 Proguard 版本的固有错误。

使用 Proguard 对逻辑操作进行 VerifyError

VerifyError on logical operations using Proguard

android

proguard

android-proguard

verifyerror