From fe049a42ad85ec39a1abb192f3eee85e1156ba4c Mon Sep 17 00:00:00 2001 From: Abhishek Arya Date: Sat, 14 Jan 2017 11:46:45 -0800 Subject: [PATCH] Update new_project_guide.md --- docs/new_project_guide.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/new_project_guide.md b/docs/new_project_guide.md index 8a9b314a3..22e19854b 100644 --- a/docs/new_project_guide.md +++ b/docs/new_project_guide.md @@ -142,15 +142,17 @@ $ python infra/helper.py build_fuzzers $PROJECT_NAME ``` This should place the built binaries into `/path/to/oss-fuzz/build/out/$PROJECT_NAME` -directory on your machine (and `$OUT` in the container). You should then try to run these binaries -inside the container to make sure that they work properly: +directory on your machine (and `$OUT` in the container). + +*Note*: You *must* run these fuzz target binaries inside the base-runner docker +container to make sure that they work properly: ```bash $ python infra/helper.py run_fuzzer $PROJECT_NAME ``` -If everything works locally, then it should also work on our automated builders -and ClusterFuzz. +If everything works locally, then it should also work on our automated builders and ClusterFuzz. +If it fails, check out [this](docs/fuzzer_environment.md#dependencies) entry. It's recommended to look at code coverage as a sanity check to make sure that [fuzz target](glossary.md#fuzz-target) gets to the code you expect.