diff options
| author |  Stefan Bucur <281483+stefanbucur@users.noreply.github.com> | 2021-01-28 11:53:18 -0500 |
|---|---|---|
| committer |  GitHub <noreply@github.com> | 2021-01-28 08:53:18 -0800 |
| commit | 41e24edb3cf43ba5ab05306627ac2333511931c9 (patch) | |
| tree | 34b3490202d4a26f04bce51b265531cde03e7c03 /docs | |
| parent | d45336243a6bd06b954c475b8ab40f76fced0feb (diff) | |
Fix argument order in run_fuzzer command example. (#5060)
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/getting-started/new_project_guide.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/getting-started/new_project_guide.md b/docs/getting-started/new_project_guide.md index d93430e3..64d4b802 100644 --- a/docs/getting-started/new_project_guide.md +++ b/docs/getting-started/new_project_guide.md @@ -322,7 +322,7 @@ You can build your docker image and fuzz targets locally, so you can test them b 3. If you want to test changes against a particular fuzz target, run the following command: ```bash - $ python infra/helper.py run_fuzzer $PROJECT_NAME <fuzz_target> --corpus-dir=<path-to-temp-corpus-dir> + $ python infra/helper.py run_fuzzer --corpus-dir=<path-to-temp-corpus-dir> $PROJECT_NAME <fuzz_target> ``` 4. We recommend taking a look at your code coverage as a test to ensure that |