Lines Matching +full:lldb +full:- +full:build

5 --------
7 LLDB has fuzzers that provide automated `fuzz testing <https://en.wikipedia.org/wiki/Fuzzing>`_ for…
10 --------------------
12 …LLDB fuzzers requires a build configuration that has the address sanitizer and sanitizer coverage …
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…
24 To build a fuzzer, run the desired ninja command for the fuzzer(s) you want to build:
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 Currently, there are plans to integrate the LLDB fuzzers into the `OSS Fuzz <https://github.com/goo…
40 -------------------
42 … fuzzers locally, you can run the binaries that were generated with ninja from the build directory:
46    $ ./bin/lldb-target-fuzzer
47    $ ./bin/lldb-commandinterpreter-fuzzer
48    $ ./bin/lldb-expression-fuzzer
52 …build the fuzzers and then run them immediately after. These custom targets run each fuzzer with c…
58    $ ninja fuzz-lldb-target
59    $ ninja fuzz-lldb-commandinterpreter
60    $ ninja fuzz-lldb-expression
63 ----------------------------------
65 …LLDB to crash, timeout or run out of memory, the input is saved to a file in the build directory. …
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: