/aosp12/frameworks/av/media/extractors/fuzzers/ |
H A D | README.md | 34 atoms are present in every input file that goes to the fuzzer. 46 Build the fuzzer 75 Build the fuzzer 109 Build the fuzzer 143 Build the fuzzer 177 Build the fuzzer 216 Build the fuzzer 247 Build the fuzzer 276 Build the fuzzer 310 Build the fuzzer [all …]
|
H A D | Android.bp | 63 name: "extractor-fuzzer-defaults", 79 name: "mpeg2-extractor-fuzzer-defaults", 80 defaults: ["extractor-fuzzer-defaults"], 120 defaults: ["extractor-fuzzer-defaults"], 146 defaults: ["extractor-fuzzer-defaults"], 169 defaults: ["extractor-fuzzer-defaults"], 189 defaults: ["extractor-fuzzer-defaults"], 213 defaults: ["extractor-fuzzer-defaults"], 261 defaults: ["extractor-fuzzer-defaults"], 281 defaults: ["extractor-fuzzer-defaults"], [all …]
|
/aosp12/art/tools/dexfuzz/src/dexfuzz/ |
H A D | DexFuzz.java | 89 Fuzzer fuzzer = null; in main() local 91 fuzzer = new FuzzerMultipleExecute(multipleListener); in main() 93 fuzzer = new FuzzerMultipleNoExecute(multipleListener); in main() 95 fuzzer = new FuzzerSingleExecute(multipleListener); in main() 97 fuzzer = new FuzzerSingleNoExecute(multipleListener); in main() 105 fuzzer.run(); in main() 106 fuzzer.printTimingInfo(); in main() 107 fuzzer.shutdown(); in main()
|
/aosp12/system/nfc/src/fuzzers/ |
H A D | README.md | 12 NCI packet parsing code -- vulnerabilites found in this fuzzer usually require 51 There are quite a lot setups required to build and run the fuzzer. To make 56 5. Building the fuzzer: 58 Here we use "nci" fuzzer as an example for building and running. The same 61 Run the following commands to build the fuzzer: 66 The above commands will build the nci fuzzer and push it to the device. 68 6. Running the fuzzer: 70 To run the fuzzer for a single iteration, assuming you are at the fuzzer 79 To run the fuzzer repeatedly, simply use the same command but without 80 "--once" option. It will keep the fuzzer running, and do the following [all …]
|
/aosp12/packages/modules/NeuralNetworks/runtime/test/fuzzing/ |
H A D | visualize_random_graph.sh | 32 DUMPSPEC=$(adb shell getprop debug.nn.fuzzer.dumpspec) 33 LOGLEVEL=$(adb shell getprop debug.nn.fuzzer.log) 44 adb shell setprop debug.nn.fuzzer.dumpspec 1 45 adb shell setprop debug.nn.fuzzer.log silence 52 adb shell setprop debug.nn.fuzzer.dumpspec $DUMPSPEC 53 adb shell setprop debug.nn.fuzzer.log $LOGLEVEL
|
/aosp12/frameworks/av/media/libstagefright/writer_fuzzers/ |
H A D | Android.bp | 50 name: "writer-fuzzer-defaults", 73 defaults: ["writer-fuzzer-defaults"], 84 defaults: ["writer-fuzzer-defaults"], 92 defaults : ["writer-fuzzer-defaults"], 103 defaults : ["writer-fuzzer-defaults"], 114 defaults : ["writer-fuzzer-defaults"],
|
H A D | README.md | 13 called `WriterFuzzerBase` to ensure code is reused between fuzzer plugins. 16 The fuzzer plugin for writers is designed based on the understanding of the 21 incoming data. This ensures more code paths are reached by the fuzzer. 50 The fuzzer plugin for AMR writer uses the `WriterFuzzerBase` class and 54 …* Two fuzzer binaries - amrnb_writer_fuzzer and amrwb_writer_fuzzer are generated based on the pre… 59 The fuzzer plugin for MPEG4 writer uses the `WriterFuzzerBase` class and 65 The fuzzer plugin for OGG writer uses the `WriterFuzzerBase` class and 71 The fuzzer plugin for WEBM writer uses the `WriterFuzzerBase` class and 76 This describes steps to build writer fuzzer binaries. 82 Build the fuzzer
|
/aosp12/build/soong/rust/ |
H A D | fuzz.go | 67 func (fuzzer *fuzzDecorator) compilerFlags(ctx ModuleContext, flags Flags) Flags { 68 flags = fuzzer.binaryDecorator.compilerFlags(ctx, flags) 77 func (fuzzer *fuzzDecorator) compilerDeps(ctx DepsContext, deps Deps) Deps { 84 deps = fuzzer.binaryDecorator.compilerDeps(ctx, deps) 89 func (fuzzer *fuzzDecorator) compilerProps() []interface{} { 90 return append(fuzzer.binaryDecorator.compilerProps(), 91 &fuzzer.Properties) 94 func (fuzzer *fuzzDecorator) stdLinkage(ctx *depsContext) RustLinkage { 98 func (fuzzer *fuzzDecorator) autoDep(ctx android.BottomUpMutatorContext) autoDep {
|
/aosp12/frameworks/av/media/codecs/m4v_h263/fuzzer/ |
H A D | README.md | 4 The fuzzer plugin for MPEG4/H263 is designed based on the understanding of the 9 bytes are present in every input file that goes to the fuzzer. 16 * If the decode operation was un-successful, the input is advanced by 1 byte so that the fuzzer 23 * Two fuzzer binaries - mpeg4_dec_fuzzer and h263_dec_fuzzer are generated based on the presence 25 * The number of decode calls are kept to a maximum of 100 so that the fuzzer does not timeout. 33 Build the fuzzer 58 The fuzzer plugin for MPEG4/H263 is designed based on the understanding of the 63 incoming data. This ensures more code paths are reached by the fuzzer. 121 that the fuzzer can proceed to feed the next frame. 134 Build the fuzzer
|
/aosp12/system/core/trusty/fuzz/ |
H A D | counters.cpp | 48 assert(fuzzer::ExtraCountersBegin()); in ExtraCounters() 49 assert(fuzzer::ExtraCountersEnd()); in ExtraCounters() 71 fuzzer::ClearExtraCounters(); in Reset()
|
/aosp12/frameworks/av/media/codecs/amrnb/enc/fuzzer/ |
H A D | README.md | 4 The fuzzer plugin for AMR-NB is designed based on the understanding of the 9 incoming data. This ensures more code paths are reached by the fuzzer. 26 that the fuzzer can proceed to feed the next frame. 39 Build the fuzzer
|
/aosp12/frameworks/av/media/codecs/amrwb/enc/fuzzer/ |
H A D | README.md | 4 The fuzzer plugin for AMR-WB is designed based on the understanding of the 9 incoming data. This ensures more code paths are reached by the fuzzer. 26 that the fuzzer can proceed to feed the next frame. 39 Build the fuzzer
|
/aosp12/hardware/interfaces/automotive/vehicle/2.0/default/tests/fuzzer/ |
H A D | README.md | 4 The fuzzer plugin for android.hardware.automotive.vehicle@2.0-manager-lib is 9 incoming data. This ensures more code paths are reached by the fuzzer. 35 Build the fuzzer 58 ##### To run the fuzzer on device
|
/aosp12/frameworks/av/media/codecs/amrnb/fuzzer/ |
H A D | README.md | 4 The fuzzer plugin for AMR-NB is designed based on the understanding of the 9 incoming data. This ensures more code paths are reached by the fuzzer. 28 that the fuzzer can proceed to feed the next frame. 41 Build the fuzzer
|
/aosp12/frameworks/av/media/codecs/amrwb/dec/fuzzer/ |
H A D | README.md | 4 The fuzzer plugin for AMR-WB is designed based on the understanding of the 9 incoming data. This ensures more code paths are reached by the fuzzer. 27 that the fuzzer can proceed to feed the next frame. 40 Build the fuzzer
|
/aosp12/art/tools/dexfuzz/ |
H A D | Android.mk | 20 .PHONY: fuzzer 22 fuzzer: dexfuzz-script $(HOST_CORE_IMG_OUTS)
|
/aosp12/frameworks/native/libs/vibrator/fuzzer/ |
H A D | README.md | 4 This fuzzer fuzzes native code present in libvibrator and does not cover the Java implementation Ex… 5 The fuzzer plugin is designed based on the understanding of the 10 incoming data. This ensures more code paths are reached by the fuzzer. 43 Build the fuzzer
|
/aosp12/frameworks/av/services/mediaresourcemanager/fuzzer/ |
H A D | README.md | 4 The fuzzer plugin for libresourcemanagerservice is designed based on the 9 incoming data. This ensures more code paths are reached by the fuzzer. 29 Build the fuzzer
|
/aosp12/frameworks/av/services/medialog/fuzzer/ |
H A D | README.md | 4 The fuzzer plugin for libmedialogservice is designed based on the understanding of the 9 incoming data. This ensures more code paths are reached by the fuzzer. 33 Build the fuzzer
|
/aosp12/frameworks/av/media/codecs/mp3dec/fuzzer/ |
H A D | README.md | 4 The fuzzer plugin for mp3 decoder is designed based on the understanding of the 9 This fuzzer makes use of the following config parameters: 35 Build the fuzzer
|
/aosp12/frameworks/av/services/camera/libcameraservice/libcameraservice_fuzzer/ |
H A D | README.md | 4 The fuzzer plugin is designed based on the understanding of the 9 incoming data. This ensures more code paths are reached by the fuzzer. 40 Build the fuzzer
|
/aosp12/frameworks/av/drm/libmediadrm/fuzzer/ |
H A D | README.md | 4 The fuzzer plugin for libmediadrm is designed based on the understanding of the 9 incoming data. This ensures more code paths are reached by the fuzzer. 39 Build the fuzzer
|
/aosp12/frameworks/av/services/mediametrics/fuzzer/ |
H A D | README.md | 4 The fuzzer plugin for libmediametricsservice is designed based on the 9 incoming data. This ensures more code paths are reached by the fuzzer. 37 Build the fuzzer
|
/aosp12/frameworks/av/media/libmediatranscoding/transcoder/tests/fuzzer/ |
H A D | README.md | 4 The fuzzer plugin for libmediatranscoder is designed based on the understanding of the 9 incoming data. This ensures more code paths are reached by the fuzzer. 42 Build the fuzzer
|
/aosp12/frameworks/av/services/audiopolicy/fuzzer/ |
H A D | README.md | 4 The fuzzer plugin for libaudiopolicy is designed based on the 9 incoming data. This ensures more code paths are reached by the fuzzer. 49 Build the fuzzer
|