Valentin Huber
Valentin Huber
> Can I have a mapper for a WrapsReference to a new WrapsReference? Yes, by passing a function that takes a reference of the origin `WrapsReference`. Currently there is no...
Let's think about this PR in three parts: 1. the mapping infrastructure itself 2. the simplified interface for `havoc_mutation` mutators that uses the above (I think we may be able...
(Still to do: comments/unit tests for mapping mutators)
Alright, cleanup done. The failing CI tests seem unrelated to what changed here, not sure what's up with them.
Alright: - Mapping mutators's names now include the name of their inner mutators - Users no longer have to specify types manually - `mapped_havoc_mutations` no longer takes a function returning...
See also #519.
While we're at it, I'm not sure why `run_target` gets a reference to the `Fuzzer`. Last I checked, this was only used in some `InProcessExecutors` to retrieve observers, and I...
> In the crash handler, we need to get fuzzer.objectives() so that's why we need fuzzer. The only thing ever needed from the fuzzer are the objectives, right? In that...
So I've tried it, and at least the libafl crate builds: #2892
Alright, it works. Ready to merge from my side. This doesn't mean this issue is to be closed, but at least the executors are a bit more disentangled from fuzzer.