| commit | 39b442cb6120c6f578495276a1e31490e4a0efbb | [log] [tgz] |
|---|---|---|
| author | Dan Zimmerman <danzimm@fb.com> | Wed Jan 15 11:45:03 2020 -0800 |
| committer | Calin Juravle <calin@google.com> | Thu Jan 16 03:13:50 2020 +0000 |
| tree | 4bada43832f4feffebd59e52c6002f35187364b8 | |
| parent | 725c54065db5b39b6a0aea7e3b3ef81280c19a6f [diff] |
[DexManager] Fix off-by-N error in DexManager when reporting dex loads In this loop the continue statement skips over incrementing dexPathIndex. In effect the classloader context that reported for a given dex file may be incorrect (specifically in the situation when the user loads a primary dex file and a secondary dex file in the same ClassLoader) Bug: 147089377 Test: atest com.android.server.pm.dex.DexManagerTests Change-Id: I7d3df507787f758537625b702131a2f4f76190e6