webdav/sync/c/open62541/tests/fuzz - 志元云盘

File OriginalPic	EditTime	Size
fuzz_binary_message_corpus	2024-12-16 13:38:58	150.2 KB
fuzz_json	2024-12-16 13:38:58	2.44 KB
check_build.sh	2024-12-16 13:38:58	272 B
CMakeLists.txt	2024-12-16 13:38:58	5.11 KB
corpus_generator.c	2024-12-16 13:38:58	24.13 KB
custom_memory_manager.c	2024-12-16 13:38:58	4.87 KB
custom_memory_manager.h	2024-12-16 13:38:58	1.08 KB
fuzz_attributeoperand.cc	2024-12-16 13:38:58	1.56 KB
fuzz_base64_decode.cc	2024-12-16 13:38:58	602 B
fuzz_base64_encode.cc	2024-12-16 13:38:58	600 B
fuzz_binary_decode.cc	2024-12-16 13:38:58	2.31 KB
fuzz_binary_message.cc	2024-12-16 13:38:58	2.33 KB
fuzz_binary_message.options	2024-12-16 13:38:58	51 B
fuzz_binary_message_header.dict	2024-12-16 13:38:58	800 B
fuzz_json_decode.cc	2024-12-16 13:38:58	761 B
fuzz_json_decode_encode.cc	2024-12-16 13:38:58	2.49 KB
fuzz_src_ua_util.cc	2024-12-16 13:38:58	1.6 KB
fuzz_src_ua_util.options	2024-12-16 13:38:58	51 B
fuzz_src_ua_util_endpoints.dict	2024-12-16 13:38:58	300 B
fuzz_tcp_message.cc	2024-12-16 13:38:58	4.7 KB
generate_corpus.sh	2024-12-16 13:38:58	3.16 KB
oss-fuzz-copy.sh	2024-12-16 13:38:58	936 B
README.md	2024-12-16 13:38:58	2.15 KB
ua_debug_dump_pkgs_file.c	2024-12-16 13:38:58	6.79 KB

I Can haz fuzz
==============

open62541 is continuously tested with the awesome oss-fuzz project from Google:
https://github.com/google/oss-fuzz

Currently tested is processing of binary messages and encoding/decoding of
binary encoded data.

Reproduce locally
-----------------

### Reproduce build failure

You can just execute the script under `tests/fuzz/check_build.sh`, which does the following:

```bash
# clone oss-fuzz repo
cd oss-fuzz
# Change $OPEN62541_DIR to your local checkout of open62541
python infra/helper.py build_fuzzers --sanitizer address open62541 $OPEN62541_DIR && python infra/helper.py check_build --sanitizer address open62541
```

### Reproduce issues

Download the testcase file and store it e.g. in your Download folder.

```bash
# clone oss-fuzz repo
cd oss-fuzz
# Change $OPEN62541_DIR to your local checkout of open62541
# And change $DOWNLOADS to your download location
python infra/helper.py build_fuzzers --sanitizer address open62541 $OPEN62541_DIR && python infra/helper.py reproduce open62541 fuzz_binary_decode $DOWNLOADS/clusterfuzz-testcase-minimized-fuzz_binary_decode-5686300273803264
```

Status
------

* [Build status](https://oss-fuzz-build-logs.storage.googleapis.com/index.html)
* [Open issues](https://bugs.chromium.org/p/oss-fuzz/issues/list?q=label:Proj-open62541)

Update the corpus
-----------------

To update the current corpus used for fuzzing you need to follow these steps.
It will execute all the unit tests, dump the received data packages to a directory
and then update and merge the corpus.

1. The script will create two directories: `open62541/build_fuzz` and `open62541/build_corpus`.
   Make sure that these directories are not existing or do not contain any important data.

2. Run the generate script:

`open62541/tests/fuzz/generate_corpus.sh`
   
   This script will build all the unit tests, dump the packages and then merge the current 
   corpus with the new packages. 
    
3. If there is new coverage with the generated data there will be new files in the directory:

`open62541/fuzz/fuzz_binary_message_corpus/generated`
   
   Commit the new files and then you can delete the build directories created in step 1.

云盘

Home / 志元云盘 / webdav / sync / c / open62541 / tests / fuzz