diff options
| author | Vladimir Marko <vmarko@google.com> | 2021-05-26 16:40:20 +0100 |
|---|---|---|
| committer | Vladimir Marko <vmarko@google.com> | 2021-06-01 09:12:04 +0100 |
| commit | 81764e5790bc9d234ac8823ed46d3c3f670f387b (patch) | |
| tree | c7fefcff95a43d10b81b8879434b0dbb1f8d25f9 /test/MultiDex | |
| parent | 9b2616bef42bb9c4fde8874c6fb3d4eeca76f2ca (diff) | |
Fix lock visiting for synchronized native methods.
The `GetGenericJniSynchronizationObject()` function was used
in the wrong context. As documented, it can be used only for
a method with a GenericJni frame and also on the top of the
stack. When visiting locks, we can have a non-GenericJni
method frame as well as a method deeper in the stack.
Replace the wrong use with specialized code.
(cherry picked from commit 654f01cd509ca11eae22177d4e764f1241fb3a53)
Test: Added regression test to 178-app-image-native-methods
Test: testrunner.py --host --debug --ndebug
Bug: 172332525
Bug: 189235039
Merged-In: Ia26f0b980c04a766e31b1588a1c011bcf46c90d8
Change-Id: I48af0e2838cda4774b8129927ea04cee9cf3a9f8
Diffstat (limited to 'test/MultiDex')
0 files changed, 0 insertions, 0 deletions