diff options
| author | Alex Light <allight@google.com> | 2018-03-05 17:48:48 -0800 |
|---|---|---|
| committer | Alex Light <allight@google.com> | 2018-03-06 09:40:08 -0800 |
| commit | 035105ff976680f11fa4fb12f1d42e2b7e250503 (patch) | |
| tree | f0e187f78fc704dc951d51921284b8fbe4fcc67f /compiler/optimizing/graph_visualizer.cc | |
| parent | 4927ba0f5011b7394e52dca2c3cec52f265f8529 (diff) | |
Ensure when NotifyMethodRedefined is called the ArtMethod is valid
Previously we were calling Jit::JitCodeCache::NotifyMethodRedefined
with an ArtMethod that was not fully valid. This could cause OOB
memory accesses if NotifyMethodRedefined attempts to access the
incorrect dex-file associated with the method at that time. This
occurs if the method is a native method. By looking at the wrong dex
file the JIT will get an incorrect MethodID and Shorty meaning it is
unable to correctly update the jit-code-cache.
Test: ./test.py --host -j50
Test: Run WIP dexmaker tests that hit this issue.
Bug: 74116990
Change-Id: Ied035b01b07d595df4037352b4bd20b42d285cb9
Diffstat (limited to 'compiler/optimizing/graph_visualizer.cc')
0 files changed, 0 insertions, 0 deletions