summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJonathan Rudenberg <jonathan@titanous.com>2018-01-19 20:10:51 -0500
committerJonathan Rudenberg <jonathan@titanous.com>2018-01-19 21:48:14 -0500
commit33d62eba912067817d33337c2bb835cec13979ad (patch)
tree24c9561a0b50acbaa8ede26cc9dcea1e01f4c5b1
parent2bd37c5be2f09950f26351506a00929c8719ea15 (diff)
downloadsystemd-33d62eba912067817d33337c2bb835cec13979ad.tar.gz
systemd-33d62eba912067817d33337c2bb835cec13979ad.tar.bz2
systemd-33d62eba912067817d33337c2bb835cec13979ad.zip
fuzz: simplify oss-fuzz build instructions in HACKING
-rw-r--r--HACKING7
1 files changed, 3 insertions, 4 deletions
diff --git a/HACKING b/HACKING
index 551216bb45..517b3c29bb 100644
--- a/HACKING
+++ b/HACKING
@@ -95,12 +95,11 @@ scripts/oss-fuzz.sh.
The fuzzers can be built locally if you have libFuzzer installed by running
scripts/oss-fuzz.sh. You should also confirm that the fuzzer runs in the
-OSS-Fuzz environment by checking out the OSS-Fuzz repo, modifying the git clone
-in projects/systemd/Dockerfile to point at your code (for example, a fork on
-GitHub) and then running these commands:
+OSS-Fuzz environment by checking out the OSS-Fuzz repo, and then running
+commands like this:
python infra/helper.py build_image systemd
- python infra/helper.py build_fuzzers --sanitizer memory systemd
+ python infra/helper.py build_fuzzers --sanitizer memory systemd ../systemd
python infra/helper.py run_fuzzer systemd fuzz-foo
For more details on building fuzzers and integrating with OSS-Fuzz, visit: