Lines Matching refs:to

5 subtle changes ("mutations") to a file to produce a new test case. These test cases
6 can be used to test the various modes of execution available to ART (Interpreter,
7 Optimizing compiler) to check for bugs in these modes of execution.
21 How to run DexFuzz
32    having DEX files pushed to it and executed with the dalvikvm command.
36    that are mutated to form new tests.
37 5. Create a directory on your device that mutated test files can be pushed to and
56 Note that if you wanted to test both ARM and ARM64 on an ARM64 device, you can use
57 --allarm. Also in this case only one backend is needed, if i.e., you wanted to test
65 Add in --device=<device name, e.g. device:generic> if you want to specify a device.
66 Add in --execute-dir=<dir on device> if you want to specify an execution directory.
75  - ANDROID_DATA must be set, pointing to a location where dex2oat will place
89 Iterations - number of attempts we've made to mutate DEX files.
90 VerifyFail - the number of mutated files that ended up failing to verify, either
92 MutateFail - because mutation is a random process, and has attempt thresholds to
93              avoid attempting to mutate a file indefinitely, it is possible that
94              an attempt to mutate a file doesn't actually mutate it. This counts
100               (use --short-timeouts to set all backends to 2 seconds.)
103              be considered a success - proper detection of crashes is still to come.
106              single backend, to check if they diverge from themselves, and these are
112    test program. This allows you to recreate a bad program with, e.g.:
125 of each mutation's probability. If you wish to easily adjust these values, copy