Catena cyber
5197f21287
fuzz: do not use inherits in Cargo.toml
...
This fixes the oss-fuzz build.
Specifically, the build log[1] showed this error:
Step #3 - "compile-libfuzzer-address-x86_64": error: inherits must
not be specified in root profile dev
So we just remove it and inline the settings.
PR #817
[1] - https://oss-fuzz-build-logs.storage.googleapis.com/log-c9b61873-8950-4a50-a729-820d5617ff7a.txt
2021-11-17 16:49:44 -05:00
Andrew Gallant
bd7466034f
fuzz: try to fix build issue
...
Ref: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=36474
See: https://oss-fuzz-build-logs.storage.googleapis.com/log-fe51f615-a13f-4685-b8d8-de4583da1ebd.txt
2021-07-23 08:39:44 -04:00
Andrew Gallant
6cdb9040f5
fuzz: bump libfuzzer-sys dependency
...
This is a half-hearted attempt to fix a build failure that I don't
understand in OSS-fuzz:
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=34294
cc @DavidKorczynski
2021-05-14 08:31:50 -04:00
DavidKorczynski
cc0f2c9064
fuzz: update libfuzzer dependency
...
This is intended to fix an OSS-fuzz build failure detailed here:
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=32817
Fixes #757
2021-04-08 10:43:47 -04:00
DavidKorczynski
a7ef5f452e
fuzz: fix release profile
...
I had to apply these changes for OSS-Fuzz to continue working.
Specifically I needed to add `cargo-features = ['named-profiles']` and
`inherits` for any profile other than `release`. However, I have also
confirmed now that the building is done with optimized + debuginfo
in OSS-Fuzz (`Finished release [optimized + debuginfo] target(s) in
37.59s`).
2020-10-14 08:55:21 -04:00
Andrew Gallant
44abc5f7c6
fuzz: enable optimizations in other profiles
...
The problem was that the fuzzer wasn't running with optimizations, which
means it was likely compiled in debug mode. So setting the optimization
level on the release profile won't do any good. Instead, we set it on
the debug and test profiles, which should cover it.
2020-10-13 19:21:47 -04:00
Andrew Gallant
9067dfd7e1
fuzz: compile fuzzer in release mode
...
Otherwise, it's pretty easy to generate regexes that are under the size
limit but take longer than the 60 second timeout in the fuzzer.
This is in response to this bug:
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26324
Actual fuzz test output:
https://oss-fuzz.com/testcase-detail/5673225499181056
2020-10-13 19:15:52 -04:00
davkor
2f9103e6bf
fuzz: add fuzzing infrastructure for OSS-Fuzz
...
Closes #679
2020-10-11 20:08:30 -04:00
