Move internal fuzz target naming scheme to g3doc
Change-Id: I400b0a34c670673aba9dd347ec41060b4b23897a
This commit is contained in:
@@ -29,17 +29,13 @@ To reproduce a crash locally for debugging:
|
||||
|
||||
1. Download the minimized testcase from the ClusterFuzz report.
|
||||
|
||||
2. In the *cdm* repository, switch branches based on the Fuzz Target prefix.
|
||||
The prefix is *oemcrypto* for the master branch, *oemcrypto_v17* for the
|
||||
oemcrypto-v17 branch, *oemcrypto_v18* for the oemcrypto-v18 branch, etc.
|
||||
|
||||
3. Build the fuzz tests:
|
||||
2. Build the fuzz tests:
|
||||
|
||||
```shell
|
||||
$ oemcrypto/test/fuzz_tests/build_oemcrypto_fuzztests
|
||||
```
|
||||
|
||||
4. Debug the crash:
|
||||
3. Debug the crash:
|
||||
|
||||
```shell
|
||||
$ gdb --args <fuzz_test_path> -timeout=0 <testcase_path>
|
||||
@@ -52,7 +48,7 @@ To reproduce a crash locally for debugging:
|
||||
clusterfuzz-testcase-minimized-oemcrypto_v17_opk_decrypt_cenc_fuzz-6727459932078080
|
||||
```
|
||||
|
||||
5. If reproducing the crash is unsuccessful, download the unminimized testcase
|
||||
4. If reproducing the crash is unsuccessful, download the unminimized testcase
|
||||
from the ClusterFuzz report and try again. If still unsuccessful, this may
|
||||
indicate there is a persistent state issue with the fuzz test.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user