Github user kcc commented on the issue:
https://github.com/apache/qpid-proton/pull/95
We use the approach with binary files in a few other repos (e.g.
https://github.com/google/boringssl/tree/master/fuzz) and it works perfect.
Note that this is not only a seed for fudzzing, but also a great way to
extend your regression testing --
just run the fuzz target (w/o fuzzing it) on all inputs in the corpus in
your pre-submit check and in CI.
If you are reluctant to store the binary files in the same repo, you may
create a separate one,
like e.g. nss does: https://github.com/mozilla/nss-fuzzing-corpus
The files should contain the exact bytes that are used to pass into the
target function,
so if you store hex (text), the target function should consume hex (text),
or otherwise you should have a conversion tools (messy)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
