Searched refs:starting (Results 1 – 21 of 21) sorted by relevance
/art/test/051-thread/ |
D | expected-stdout.txt | 2 thread test starting 4 testThreadDaemons starting thread 'TestDaemonThread' 10 testSetName starting 13 testThreadPriorities starting
|
/art/test/050-sync-test/ |
D | expected-stdout.txt | 31 SleepyThread.run starting 32 SleepyThread.run starting
|
/art/tools/jvmti-agents/ti-alloc-sample/ |
D | README.md | 53 Lines starting with a + are key, value pairs. So, for instance, key 2 stands for 59 The line starting with 0 is the thread, type, and size (TTS) of an allocation. The 60 remaining lines starting with + are stack frames (SFs), containing function signatures. 61 Lines starting with = are stack traces (STs), and are again key, value pairs. In the 62 example above, an ST called 16 is the TTS plus sequence of SFs. Any line not starting
|
/art/test/1934-jvmti-signal-thread/ |
D | expected-stdout.txt | 2 interrupting other thread before starting 5 stopping other thread before starting
|
/art/test/004-checker-UnsafeTest18/ |
D | expected-stdout.txt | 1 starting
|
/art/test/067-preemptive-unpark/ |
D | expected-stdout.txt | 1 Test starting
|
/art/test/2031-zygote-compiled-frame-deopt/src/art/ |
D | Test2031.java | 25 public void starting() { in starting() method in Test2031.MyClass 52 myObject.starting(); in $noinline$startTest()
|
/art/test/001-Main/ |
D | info.txt | 1 Import of a previous oat test. Empty main, just test starting up the runtime.
|
/art/test/033-class-init-deadlock/ |
D | expected-stdout.txt | 1 Deadlock test starting.
|
/art/build/apex/ |
D | art.rc | 19 disabled # Prevents the service from automatically starting at boot. 36 disabled # Prevents the service from automatically starting at boot. 48 disabled # Prevents the service from automatically starting at boot.
|
/art/test/099-vmdebug/ |
D | expected-stdout.txt | 8 Test starting when already started
|
/art/test/083-compiler-regressions/ |
D | expected-stdout.txt | 8 b13679511Test starting
|
/art/test/546-regression-simplify-catch/smali/ |
D | TestCase.smali | 62 # starting with a move-exception. Verifier does not check trivially dead code 82 # starting with a move-exception. Verifier does not check trivially dead code
|
/art/tools/ |
D | run-gtests.sh | 26 absolute paths (starting with /apex). All gtests are run otherwise.
|
/art/test/802-deoptimization/smali/ |
D | catch_handler_on_entry.smali | 5 # Test we can execute a method starting with a catch handler (without
|
/art/tools/build/ |
D | var_list | 19 # Lines starting with '#' or blank lines are ignored.
|
/art/runtime/interpreter/mterp/ |
D | README.txt | 7 * Lines starting with % are python code. They will be copied as-is to 23 The starting label will be provided by the generation tool, as will
|
/art/imgdiag/ |
D | dirty_image_objects.md | 54 a reference chain starting from a class. Example:
|
/art/tools/runtime_memusage/ |
D | README | 18 Files are marked for poisoning, their starting addresses are logged in logcat.
|
/art/test/ |
D | README.atest.md | 19 ART run-tests are defined in sub-directories of `test/` starting with a number
|
/art/runtime/ |
D | mutator_gc_coord.md | 156 acquiring the mutator lock, e.g. either by starting a `ScopedObjectAccess`, or
|