aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChelsea Cassanova <chelsea@cassanova.me>2022-08-26 20:06:44 -0500
committerChelsea Cassanova <chelsea@cassanova.me>2022-08-26 22:15:38 -0500
commit53f1cc85e3de11ff91eb985332257d63dcf47ddc (patch)
tree110dbb3f732bb7b51d21477c4737301ecda9f8dd
parentab492f628216fbca2ae2a24c8fd61ca3f9f70a04 (diff)
downloadllvm-53f1cc85e3de11ff91eb985332257d63dcf47ddc.zip
llvm-53f1cc85e3de11ff91eb985332257d63dcf47ddc.tar.gz
llvm-53f1cc85e3de11ff91eb985332257d63dcf47ddc.tar.bz2
[lldb][docs] Fix formatting in fuzzing doc
The page for fuzzing LLDB had incorrectly formatted code, this commit fixes that. Differential revision: https://reviews.llvm.org/D132775
-rw-r--r--lldb/docs/resources/fuzzing.rst5
1 files changed, 5 insertions, 0 deletions
diff --git a/lldb/docs/resources/fuzzing.rst b/lldb/docs/resources/fuzzing.rst
index 7c106f4..2b1e7bd 100644
--- a/lldb/docs/resources/fuzzing.rst
+++ b/lldb/docs/resources/fuzzing.rst
@@ -12,6 +12,7 @@ Building the fuzzers
Building the LLDB fuzzers requires a build configuration that has the address sanitizer and sanitizer coverage enabled. In addition to your regular CMake arguments, you will need these argumets to build the fuzzers:
::
+
-DLLVM_USE_SANITIZER='Address' \
-DLLVM_USE_SANITIZE_COVERAGE=On \
-DCLANG_ENABLE_PROTO_FUZZER=ON
@@ -23,6 +24,7 @@ If you want to debug LLDB itself when you find a bug using the fuzzers, use the
To build a fuzzer, run the desired ninja command for the fuzzer(s) you want to build:
::
+
$ ninja lldb-target-fuzzer
$ ninja lldb-commandinterpreter-fuzzer
$ ninja lldb-expression-fuzzer
@@ -40,6 +42,7 @@ Running the fuzzers
If you want to run the fuzzers locally, you can run the binaries that were generated with ninja from the build directory:
::
+
$ ./bin/lldb-target-fuzzer
$ ./bin/lldb-commandinterpreter-fuzzer
$ ./bin/lldb-expression-fuzzer
@@ -51,6 +54,7 @@ Another way to run the fuzzers is to use a ninja target that will both build the
To run the custom ninja targets, run the command for your desired fuzzer:
::
+
$ ninja fuzz-lldb-target
$ ninja fuzz-lldb-commandinterpreter
$ ninja fuzz-lldb-expression
@@ -65,4 +69,5 @@ When running the fuzzers using the custom ninja targets shown above, the inputs
If you want to reproduce the issue found by a fuzzer once you have gotten the input, you can pass the individual input to the fuzzer binary as a command-line argument:
::
+
$ ./<fuzzer binary> <input you are investigating>