Aarnav
Aarnav
@rmalmain is this a Rust (libafl-fuzz / libafl_nyx) issue or a AFL++ one?
Could you please try again?
@rmalmain thanks. I'll need to have a look myself cause this is compiling just fine on my Intel THinkpad with clang-18 (just no kvm stuff so it won't actually run)....
Ah I see. Thanks @rmalmain
Would this be something you are capable of contributing @kevin-valerio ?
@selvanair @alonbl the fix also looks good from the fuzzing side!
Hey Addison, Since I implemented the feedback hit tracking I have a question regarding this issue: What would be the benefit of having a wrapper type? This will add another...
But the very nature of the feature implies that every Feedback must implement it? But I agree that Feedbacks need a re-visit, as there are too many static Feedbacks and...
``Fuzzer::evaluate_input`` should be used instead? Maybe the reasoning was to avoid new corpus entries? but if there's new coverage, why not add it to corpus?
Yeah, I wanted to keep it in line with AFL++ but I'll change it