diff options
| author | Dr. David von Oheimb <David.von.Oheimb@siemens.com> | 2020-07-03 14:19:43 +0200 |
|---|---|---|
| committer | Dr. David von Oheimb <David.von.Oheimb@siemens.com> | 2020-07-16 21:44:26 +0200 |
| commit | cb9bb7350d4192553683e61e64894e8ed197b44c (patch) | |
| tree | f296ea1944f61978d43d87eceeb0f110cd3c15c1 /fuzz | |
| parent | 1e76cb002a8d89b66b67214921b921c4cb9f6506 (diff) | |
| download | openssl-new-cb9bb7350d4192553683e61e64894e8ed197b44c.tar.gz | |
99-test_fuzz.t: Clean up and re-organize such that sub-tests could be split easily
Reviewed-by: Richard Levitte <levitte@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/12359)
Diffstat (limited to 'fuzz')
| -rw-r--r-- | fuzz/README.md | 16 |
1 files changed, 15 insertions, 1 deletions
diff --git a/fuzz/README.md b/fuzz/README.md index a713f85325..deb7a43168 100644 --- a/fuzz/README.md +++ b/fuzz/README.md @@ -99,7 +99,7 @@ Reproducing issues If a fuzzer generates a reproducible error, you can reproduce the problem using the fuzz/*-test binaries and the file generated by the fuzzer. They binaries -don't need to be build for fuzzing, there is no need to set CC or the call +don't need to be built for fuzzing, there is no need to set CC or the call config with enable-fuzz-* or -fsanitize-coverage, but some of the other options above might be needed. For instance the enable-asan or enable-ubsan option might be useful to show you when the problem happens. For the client and server fuzzer @@ -110,6 +110,20 @@ To reproduce the crash you can run: fuzz/$FUZZER-test $file +To do all the tests of a specific fuzzer such as asn1 you can run + + fuzz/asn1-test fuzz/corpora/asn1 +or + make test TESTS=fuzz_test FUZZ_TESTS=asn1 + +To run several fuzz tests you can use for instance: + + make test TESTS=test_fuzz FUZZ_TESTS="cmp cms" + +To run all fuzz tests you can use: + + make test TESTS=test_fuzz + Random numbers -------------- |