diff options
| author | David Brazdil <dbrazdil@google.com> | 2019-03-04 15:59:06 +0000 |
|---|---|---|
| committer | David Brazdil <dbrazdil@google.com> | 2019-04-02 19:20:14 +0000 |
| commit | 35a3f6a09931ee631a0377ee3ca98a7fb1f4f61d (patch) | |
| tree | c3bbc93f5d7c5c74b49a03fc9a2609f7a918840e /test/008-exceptions/src/MultiDexBadInitWrapper1.java | |
| parent | 3bfc694a4bcc9ef3de19b94a34701c76c6008071 (diff) | |
Create vdex file for dex loaded with InMemoryDexClassLoader
Previous CL introduced a background verification thread for dex bytecode
loaded with InMemoryDexClassLoader. Extend the logic to collect the
results of class verification into an instance of VerifierDeps and dump
it into a vdex file in the app's data folder.
The background thread does not collect full VerifierDeps (e.g.
assignability dependencies, etc), just a bit vector of whether a class
was successfully verified or not.
The vdex format is extended to include boot classpath checksums and the
class loader context it was created for. These are optional and
currently left empty for regular vdex files.
The generated vdex files are treated as a cache with a limited capacity,
currently capped at 8 files. The least recently used file (in terms of
atime reported by stat()) is unlinked if the cache is full and a new
vdex is about to be generated.
Bug: 72131483
Test: art/tools/run-libcore-tests.sh
Test: art/test.py -b -r -t 692 -t 693
Change-Id: I26080d894d34d8f35f00c7925db569f22f008d2c
Diffstat (limited to 'test/008-exceptions/src/MultiDexBadInitWrapper1.java')
0 files changed, 0 insertions, 0 deletions