KillingSpark / KillingSpark/zstd-rs

Any difference between decodecorpus_files and fuzz_decodecorpus?

Open
#5 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
449
Forks
66
PR merge metrics
No merged PRs in 30d

Description

I'm looking to fuzz the library more and use the fuzzer to compare the output to the reference C implementation. I've been wondering, what's the difference between the two directories with inputs - decodecorpus_files and fuzz_decodecorpus?

Also, you can make cargo-fuzz automatically pick up the fuzzing corpus without requiring to explicitly specify a path if you move it to `fuzz/corpus/fuzz_target_1`, similar to `artifacts` folder.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by comparing the decodecorpus_files and fuzz_decodecorpus directories and checking how the cargo-fuzz target currently discovers inputs, including the existing artifacts folder. Done means documenting or resolving the directory distinction and determining whether the corpus belongs under fuzz/corpus/fuzz_target_1 for automatic discovery.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
testing
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.