27428b1369
git-svn-id: http://svn.osgeo.org/postgis/trunk@15793 b70326c6-7e19-0410-871a-916f4a2858ee
39 lines
1.5 KiB
Plaintext
39 lines
1.5 KiB
Plaintext
This directory contains fuzzer main functions and scripts for the
|
|
Google OSS Fuzz project: https://github.com/google/oss-fuzz/
|
|
|
|
The main build scripts are in:
|
|
https://github.com/google/oss-fuzz/tree/master/projects/postgis
|
|
and call scripts in this directory.
|
|
|
|
The list of issues is in:
|
|
https://bugs.chromium.org/p/oss-fuzz/issues/list?q=postgis
|
|
|
|
- Simulate the build of (dummy) fuzzers like OSS Fuzz does:
|
|
$ make dummyfuzzers
|
|
They are created in /tmp/*_fuzzer as well as with the
|
|
/tmp/*_fuzzer_seed_corpus.zip files
|
|
|
|
Run one:
|
|
$ /tmp/wkt_import_fuzzer a_file_name
|
|
|
|
- Run locally OSS Fuzz:
|
|
$ git clone --depth=1 https://github.com/google/oss-fuzz.git
|
|
$ cd oss-fuzz
|
|
$ python infra/helper.py build_image postgis
|
|
|
|
Build fuzzers with the address sanitizer (could use undefined, etc...)
|
|
$ python infra/helper.py build_fuzzers --sanitizer address postgis
|
|
|
|
Test a particular fuzzer (replace wkt_import_fuzzer by other fuzzers
|
|
like the ones generated in /tmp by "make dummyfuzzers")
|
|
$ python infra/helper.py run_fuzzer postgis wkt_import_fuzzer
|
|
|
|
|
|
How to deal with issues reported in https://bugs.chromium.org/p/oss-fuzz/issues/list?q=postgis ?
|
|
|
|
1. Leave a comment in (chromium database) bug entry to indicate that you work on it
|
|
2. Work
|
|
3. Commit a bug fix with log including "Credit to OSS-Fuzz" and a link to the bugs.chromium.org ticket
|
|
4. Add in the bugs.chromium.org ticket a link to the Trac changeset implementing the fix.
|
|
5. Check chromium closed the bug (after one or two days typically)
|