Fossil SCM
Add a warning in build.wiki that passing fuzzer-specific flags may cause the --fuzztype flag to get stripped from the argument list.
Commit
df1d2569223045f377f60a2870dd269ae9ca0dc375743c82b40488067fbc643d
Parent
2c8920296cb4471…
1 file changed
+6
-2
+6
-2
| --- www/build.wiki | ||
| +++ www/build.wiki | ||
| @@ -454,7 +454,11 @@ | ||
| 454 | 454 | For a detailed information about the fuzzer's flags and features, see: |
| 455 | 455 | |
| 456 | 456 | * [https://llvm.org/docs/LibFuzzer.html] |
| 457 | 457 | * [https://github.com/google/fuzzing/blob/master/tutorial/libFuzzerTutorial.md] |
| 458 | 458 | |
| 459 | -Flags for the fuzzer can be passed directly to fossil, e.g. <tt>-jobs=4</tt> | |
| 460 | -to start four fuzzer jobs in parallel. | |
| 459 | +Flags for the fuzzer can be passed directly to fossil, | |
| 460 | +e.g. <tt>-jobs=4</tt> to start four fuzzer jobs in parallel, but doing | |
| 461 | +so may cause the fuzzer to <em>strip the --fuzztype flag</em>, leading | |
| 462 | +to it testing the wrong thing. When passing on fuzzer-specific flags | |
| 463 | +along with <tt>--fuzztype</tt>, be sure to check your system's process | |
| 464 | +list to ensure that your <tt>--fuzztype</tt> flag is there. | |
| 461 | 465 |
| --- www/build.wiki | |
| +++ www/build.wiki | |
| @@ -454,7 +454,11 @@ | |
| 454 | For a detailed information about the fuzzer's flags and features, see: |
| 455 | |
| 456 | * [https://llvm.org/docs/LibFuzzer.html] |
| 457 | * [https://github.com/google/fuzzing/blob/master/tutorial/libFuzzerTutorial.md] |
| 458 | |
| 459 | Flags for the fuzzer can be passed directly to fossil, e.g. <tt>-jobs=4</tt> |
| 460 | to start four fuzzer jobs in parallel. |
| 461 |
| --- www/build.wiki | |
| +++ www/build.wiki | |
| @@ -454,7 +454,11 @@ | |
| 454 | For a detailed information about the fuzzer's flags and features, see: |
| 455 | |
| 456 | * [https://llvm.org/docs/LibFuzzer.html] |
| 457 | * [https://github.com/google/fuzzing/blob/master/tutorial/libFuzzerTutorial.md] |
| 458 | |
| 459 | Flags for the fuzzer can be passed directly to fossil, |
| 460 | e.g. <tt>-jobs=4</tt> to start four fuzzer jobs in parallel, but doing |
| 461 | so may cause the fuzzer to <em>strip the --fuzztype flag</em>, leading |
| 462 | to it testing the wrong thing. When passing on fuzzer-specific flags |
| 463 | along with <tt>--fuzztype</tt>, be sure to check your system's process |
| 464 | list to ensure that your <tt>--fuzztype</tt> flag is there. |
| 465 |