Lines Matching +full:built +full:- +full:docs

5 --------
7 …>`_ for different components of LLDB. The fuzzers are built with `libFuzzer <https://llvm.org/docs…
10 --------------------
16    -DLLVM_USE_SANITIZER='Address' \
17    -DLLVM_USE_SANITIZE_COVERAGE=On \
18    -DCLANG_ENABLE_PROTO_FUZZER=ON
20 …zzer's sanitizer coverage is available here: `<https://llvm.org/docs/LibFuzzer.html#fuzzer-usage>`_
22 If you want to debug LLDB itself when you find a bug using the fuzzers, use the CMake option ``-DCM…
28    $ ninja lldb-target-fuzzer
29    $ ninja lldb-commandinterpreter-fuzzer
30    $ ninja lldb-expression-fuzzer
32 Once built, the binaries for the fuzzers will exist in the ``bin`` directory of your build folder.
35 ----------------------
37 …integrate the LLDB fuzzers into the `OSS Fuzz <https://github.com/google/oss-fuzz>`_ project for c…
40 -------------------
46    $ ./bin/lldb-target-fuzzer
47    $ ./bin/lldb-commandinterpreter-fuzzer
48    $ ./bin/lldb-expression-fuzzer
50 …naries directly, and you can use the `libFuzzer options <https://llvm.org/docs/LibFuzzer.html#opti…
52 …un them immediately after. These custom targets run each fuzzer with command-line arguments that p…
58    $ ninja fuzz-lldb-target
59    $ ninja fuzz-lldb-commandinterpreter
60    $ ninja fuzz-lldb-expression
63 ----------------------------------
65 …g the fuzzer binaries directly this input is stored in a file named ``<crash/timeout/oom>-<hash>``.
67 …r-artifacts/<fuzzer name>-artifacts``, which is created in your build directory. The input files w…
69 …otten the input, you can pass the individual input to the fuzzer binary as a command-line argument: