Use libfuzzer instead of honggfuzz#5315
Conversation
|
Can you PR separately to delete the fuzz seeds? It will make it easier to review this. Later we should make a |
|
Sorry, was out for a bit on vacation but removed the files. I'm gonna keep it as a draft as I work through fixing the tests hopefully this week/weekend |
3567ce3 to
9922cfc
Compare
54a7ecc to
40938b3
Compare
|
It would be very difficult -- probably I would need to fork |
ef8bebf to
17eccb3
Compare
|
@apoelstra ok, i added the |
|
17eccb3 looks reasonable to me.
./generate-files.sh
error: no such command: `fuzz`
help: a command with a similar name exists: `hfuzz`
help: view all installed commands with `cargo --list`
help: find a package to install `fuzz` with `cargo search cargo-fuzz` |
|
@tcharding i think you will need to have cargo fuzz installed via |
|
Indeed - face palm. Thanks mate. |
|
@apoelstra were you able to run your local CI against this branch after i added the fuzzing flag? |
|
I didn't try because it fell to the back of my queue, sorry. Can you rebase it? |
|
Rebased |
af1423b to
3ad3f35
Compare
|
Heh, these Zizimor errors are pretty interesting. Unsure why they're showing up here and not elsewhere. In 3ad3f35: This still adds |
This commit has a few main parts: - Update CI to install required dependencies for libfuzzer The default Cross s390x image uses an older version of GCC (Ubuntu 20.04), which lacks std::clamp needed by libfuzzer-sys. The s390x Dockerfile provides Cross with a container with GCC 13, native build tools, and QEMU for running s390x tests. Cross.toml configures Cross to use this custom image instead of the default. - Update the lock files - Update the fuzz targets to use libfuzzer - Update the fuzz helper scripts and documentation - Update the duplicate dependency whitelist to include libc - Move `fuzz` into a nested workspace
|
Removed from It looks like the zizmor stuff is popping up cause this is updating CI. They aren't related to this PR, but I created #5833 to track |
This commit has a few main parts:
Update CI to install required dependencies for libfuzzer
The default Cross s390x image uses an older version of GCC (Ubuntu
20.04), which lacks std::clamp needed by libfuzzer-sys. The s390x
Dockerfile provides Cross with a container with GCC 13, native build
tools, and QEMU for running s390x tests. Cross.toml configures Cross to
use this custom image instead of the default.
Update the lock files
Update the fuzz targets to use libfuzzer
Update the fuzz helper scripts and documentation
Update the duplicate dependency whitelist to include libc
I was able to test that the fuzz scripts were working locally on my Mac and on a Docker container running Ubuntu.
Closes #3265