summaryrefslogtreecommitdiff
path: root/compiler/common_compiler_test.cc
diff options
context:
space:
mode:
authorAlex Light <allight@google.com>2021-01-27 16:14:30 -0800
committerTreehugger Robot <treehugger-gerrit@google.com>2021-01-29 18:08:20 +0000
commit0fba186013badc1526ae5c34e1e59c39f06ad43c (patch)
tree41d6c281a267623ccbf881ec9664acb43281540e /compiler/common_compiler_test.cc
parent60e0081a6b7ee2e6daafb0f82d3154ad86bcde71 (diff)
Add ERROR log with JVMTI version explanation
We semi-regularly get bugs where people report being unable to get JVMTI on non-debuggable processes running on userdebug/eng devices. This new log line will help anyone who hits this have a better idea of next steps hopefully. The confusion is mostly around assuming that if JVMTI isn't available the attachAgent function will throw and the Agent_OnAttach function will not be called. While this is true for 'user' builds on 'userdebug' and 'eng' we will allow the agent to start but if the processes is not debuggable only kArtTiVersion (0x70010200) jvmtiEnvs can be created. These envs have somewhat looser specifications then the normal jvmtiEnvs and are used to provide best-effort debugger support on userdebug, among other things. Test: manual Bug: 178033907 Change-Id: I03993ae5200e5d308180014f6fedb3d2062c0d77
Diffstat (limited to 'compiler/common_compiler_test.cc')
0 files changed, 0 insertions, 0 deletions