Don't use oat / runtime app images in debuggable runtimes
Oat code even when compiled in debuggable mode lacks method entry / exit
hooks. While runtime app images could be potentially used in debuggable
runtimes, they don't impact the performance much. So to keep things
simple, just don't load images in debuggable runtimes.
Also, fix the entrypoints when initializing the classes. This is
strictly not necessary but a safe thing to do.
Test: art/testrunner.py --speed --debuggable
Change-Id: I1c2b5c54a634ff3cde7f46f1077b5e16db2ecb0e
5 files changed