Lines Matching refs:and

9 execution, and any differences between the resulting outputs may be an indication of
17 for mutation - e.g. some tests taken from the ART test suite - and point it at an
18 ADB-connected Android device, and it will fuzz these seed files, and execute the
32    having DEX files pushed to it and executed with the dalvikvm command.
35 4. Create a new directory, and place some DEX files in here. These are the seed files
37 5. Create a directory on your device that mutated test files can be pushed to and
44     --dump-output <combination of ISA(s) and and backend(s)>
56 Note that if you wanted to test both ARM and ARM64 on an ARM64 device, you can use
73 Follow steps 1, 3, 4, and 7 as above, but also observe the following:
92 MutateFail - because mutation is a random process, and has attempt thresholds to
101 Successful - mutated files that executed and all backends agreed on the resulting
104 Divergence - mutated files that executed and some backend disagreed about the
106              single backend, to check if they diverge from themselves, and these are
108              (ARM/ARM64), and the divergences align with different architectures,
111 8. Check report.log for the full report, including input file and RNG seed for each
118 NOTE: DEX files with unicode strings are not fully supported yet, and DEX files with
126 these values into a file called likelihoods.txt, and run dexfuzz with