s1341
s1341
I think that a proper logging library would be very useful. If possible, it should prefix output with a date/time-stamp and a thread/process id...
I think a proper logging crate is definitely necessary. Can we think of a way to date/time-stamp and process-id-stamp the `dup2`-ed output from launcher when `--output` is used? Is there...
Note that we will have to return an appropriate ExitKind to cause the executor/stage to save the test case into the objective corpus. Is this currently possible @andreafioraldi?
Currently loading from an OnDiskCorpus is quite horrific, especially when running ('resuming') on multiple cores. It takes forever and each core sends all testcases to every other core.... We need...
After running a fuzz-campaign for about a week with LibAFL, it's clear to me that some way to stop and resume the fuzzing, potentially with tweaks to the fuzzer in...
> It was giving problem because of this panic. > > > panic!("Fuzzer-respawner: Storing state in crashed fuzzer instance did not work, no point to spawn the next client!"); >...
@andreafioraldi has started work on this, by adding the ability to append metadata from Observers to solutions.
We still don't have unique names for the test-cases. We also don't have 'default metadata' including timestamp, cmd-line used to generate the test case, mutations applied, parent case etc.
I have tons of files in my tempdir.... something is fishy...
Huh... why are they not cleared after read?