jonathanmetzman
jonathanmetzman
>Is it possible to remove fuzzbench local experiment limitations of the number of fuzzers and benchmarks? Short of implementing proper local support (which probably won't come before January) I think...
> What's the state of this issue @jonathanmetzman? On a 64 gb ram and 64 cores VM I cannot start a local experiment with 4 fuzzers and 3 benchs, I'm...
What are the specs of your machine? How many cores and how much RAM? I think this issue is https://github.com/moby/moby/issues/36324 If this is the case, adding in some resource control...
Hmmm...Maybe not then. One possible issue with builds on a single machine could be that each docker build might use as many cores as possible (e.g. `make -j $NPROC`). Maybe...
> Fuzzbench distinguishes runner and measurer and only the seed corpus ever reaches the measurer. So, getting coverage statistics right from the fuzzing process might be a bit more difficult....
>The above loop checks all covered regions in each function and construct the code locations (starting and ending line/column, file id, etc.) that have been executed. I'd like to understand...
I think you mean for local experiments right? Yeah I need to think of a way to surface logs.
This is a good idea. Lemme figure this out. Sorry for the late reply, I was traveling a lot
Sorry for the delay on this. I will try to look tomorrow
Sorry, I don't think I want to add so many files to fuzzbench