Searched refs:fuzzers (Results 1 – 25 of 43) sorted by relevance
12
| /external/adhd/cras/src/fuzz/ |
| D | README | 2 fuzzers.
14 Build fuzzers
16 $ sudo docker run -ti --rm -v $(pwd):/src/cras -v /tmp/fuzzers:/out \
19 Look in /tmp/fuzzers to see the executables. Run them like so:
22 -v /tmp/fuzzers:/out ossfuzz/base-runner /out/rclient_message \
|
| D | Dockerfile | 5 # Defines a docker image that can build cras fuzzers.
|
| /external/libchrome/mojo/public/tools/fuzzers/ |
| D | BUILD.gn | 13 group("fuzzers") {
31 seed_corpus = "//mojo/public/tools/fuzzers/message_corpus"
60 seed_corpus = "//mojo/public/tools/fuzzers/mojo_parse_message_proto_corpus"
|
| /external/libchrome/mojo/public/ |
| D | BUILD.gn | 29 group("fuzzers") {
31 "tools/fuzzers",
|
| /external/swiftshader/third_party/llvm-7.0/llvm/docs/ |
| D | FuzzingLLVM.rst | 12 The LLVM tree includes a number of fuzzers for various components. These are
178 Some of the in-tree fuzzers that use this type of mutator are `clang-fuzzer`_,
198 :ref:`building-fuzzers`.
211 We also use a more direct form of structured fuzzing for fuzzers that take
224 .. _building-fuzzers:
231 one sanitizer to find bugs faster. The most common way to build the fuzzers is
242 There used to be a public buildbot running LLVM fuzzers continuously, and while
263 There are some utilities available for writing fuzzers in LLVM.
270 There is also some handling of the CMake config for fuzzers, where you should
|
| /external/v8/tools/testrunner/ |
| D | num_fuzzer.py | 217 fuzzers = []
220 fuzzers.append(fuzzer.create_fuzzer_config(name, prob, *args))
229 return fuzzers
|
| /external/boringssl/src/ |
| D | FUZZING.md | 17 From the `build/` directory, you can then run the fuzzers. For example:
52 …MINISTIC_MODE` defined. This modifies the library to be more friendly to fuzzers. If `BORINGSSL_UN…
54 …th a deterministic PRNG. Call `RAND_reset_for_fuzzing()` at the start of fuzzers which use `RAND_b…
74 …zzer_mode` and `server_corpus_no_fuzzer_mode`. These are transcripts for fuzzers with only `BORING…
|
| /external/grpc-grpc/tools/fuzzer/runners/ |
| D | server_fuzzer.sh | 31 bins/$config/server_fuzzer $flags fuzzer_output test/core/end2end/fuzzers/server_fuzzer_corpus
|
| D | api_fuzzer.sh | 31 bins/$config/api_fuzzer $flags fuzzer_output test/core/end2end/fuzzers/api_fuzzer_corpus
|
| D | client_fuzzer.sh | 31 bins/$config/client_fuzzer $flags fuzzer_output test/core/end2end/fuzzers/client_fuzzer_corpus
|
| /external/perfetto/infra/oss-fuzz/ |
| D | build_fuzzers | 17 $SRC/perfetto/tools/ninja -C $WORK/build fuzzers -v
|
| /external/syzkaller/syz-manager/ |
| D | manager.go | 80 fuzzers map[string]*Fuzzer member
179 fuzzers: make(map[string]*Fuzzer),
897 mgr.fuzzers[a.Name] = f
953 f := mgr.fuzzers[a.Name]
985 for _, f1 := range mgr.fuzzers {
1010 f := mgr.fuzzers[a.Name]
1017 for _, f1 := range mgr.fuzzers {
|
| /external/v8/tools/testrunner/testproc/ |
| D | fuzzer.py | 48 def __init__(self, rng, count, fuzzers, disable_analysis=False): argument
61 self._fuzzer_configs = fuzzers
|
| /external/skqp/fuzz/ |
| D | coverage | 14 where afl-out is the directory containing all the output of the afl-fuzzers.
|
| /external/skia/fuzz/ |
| D | coverage | 14 where afl-out is the directory containing all the output of the afl-fuzzers.
|
| /external/grpc-grpc/test/core/end2end/fuzzers/ |
| D | BUILD | 17 grpc_package(name = "test/core/end2end/fuzzers")
|
| /external/webrtc/webrtc/ |
| D | BUILD.gn | 291 # webrtc/test/fuzzers/.
295 "test/fuzzers:webrtc_fuzzer_main",
|
| /external/swiftshader/third_party/SPIRV-Tools/test/fuzzers/ |
| D | BUILD.gn | 22 group("fuzzers") {
|
| /external/deqp-deps/SPIRV-Tools/test/fuzzers/ |
| D | BUILD.gn | 22 group("fuzzers") {
|
| /external/perfetto/ |
| D | BUILD.gn | 81 deps += [ ":fuzzers" ]
297 group("fuzzers") {
|
| /external/boringssl/src/util/ |
| D | generate_build_files.py | 315 fuzzers = [os.path.splitext(os.path.basename(fuzzer))[0]
317 self.PrintVariableSection(out, 'fuzzers', fuzzers)
|
| /external/swiftshader/ |
| D | BUILD.gn | 160 "tests/fuzzers/VertexRoutineFuzzer.cpp"
|
| /external/pcre/dist2/ |
| D | NEWS | 168 strange pattern input, and were discovered by fuzzers. Some others were
222 6. Bugs have been mended, many of them discovered by fuzzers.
|
| /external/honggfuzz/ |
| D | README.md | 10 …or processes (e.g. _ptrace_ under Linux and NetBSD). As opposed to other fuzzers, it __will discov…
12 …ggfuzz/blob/master/docs/FeedbackDrivenFuzzing.md) methods known from other fuzzers (libfuzzer, afl)
|
| /external/llvm/docs/ |
| D | LibFuzzer.rst | 113 Coverage-guided fuzzers like libFuzzer rely on a corpus of sample inputs for the
635 Both fuzzers expect the test corpus to reside in a directory, one file per input.
636 You can run both fuzzers on the same corpus, one after another:
643 Periodically restart both fuzzers so that they can use each other's findings.
780 fuzzers. The fuzzer arguments should follow ``--fuzzer-args`` and should have
791 A buildbot continuously runs the above fuzzers for LLVM components, with results
|
12