Repository navigation
Conversation
|
Hi @manas765 , thanks for the PR! this doesn't look ready to merge yet - before we review this in detail could you justify this change in your PR description? It's not clear so far what you think others should use this for or what bugs you've found using it. |
james-rms
left a comment
There was a problem hiding this comment.
On second thought, I don't think we're ready to merge this without some further agreement on the high-level approach we would take to fuzzing the libraries. Keeping a fuzzing harness upstream isn't useful IMO unless we're regularly exercising it along with new changes to the library, and that the approach is compatible with the libraries for all languages.
|
Thanks for picking this up — the three targets here cover the linear paths and the summary parser called for in #1907 well. One gap worth considering while this is open: an |
Summary
MessageStream,Summary::read, andLinearReader.rust/fuzzwith an independent Cargo workspace.Testing
cargo +nightly fuzz build.cargo fmt --manifest-path rust/fuzz/Cargo.toml -- --check.Note: Fuzz target execution on Windows is currently blocked by a runtime DLL error (
STATUS_DLL_NOT_FOUND). The targets compile, but successful fuzzing runs have not yet been verified.