If you still don’t understand why there are uninstrumented calls or methods, you can also turn on the instrumentation traces, as well as additional checks, by adding respectively the v, d and c arguments to the Java agent (the corresponding AOT instrumentation task options are verbose, debug and check respectively). This will print thoroughly all the steps of Quasar’s instrumentation process, including which methods calls are considered suspendable (or aren’t, and why) and which are actually instrumented (or aren’t, and why).
Reference
我在
build.gradle
中有以下一行:tasks.withType(JavaExec)
{
jvmArgs "-javaagent:${configurations.quasar.iterator().next()}"
}
如何将参数传递给Java Agent?我尝试了一些方法,但没有任何效果。
最佳答案
在最后添加:
tasks.withType(JavaExec)
{
jvmArgs "-javaagent:${configurations.quasar.iterator().next()}=vdc"
}
关于java - 如何在Gradle中启用Java代理调试?,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/40551133/