Andrea Fioraldi

I got a lof of errors in #1330 as adding benchmarks triggers the CI for every fuzzer and I spotted several issues: + lafintel is broken because it uses llvm...

I confirm that symcc_aflplusplus fails on matio too, this time because -pthread is missing. I guess this simply happens because clang is linking while the symcc runtime is in C++,...

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 stuck...

Ok so currently there isn't a memory limit?

Ok so it is possible that a fuzzer doesn't detect a bug but it is reported in the report? You should check crashes only in the crashes/ folder IMHO, but...

I still don't get why in the report I have 0 bugs for an AFL++ based fuzzer but when I look at results/fuzzer-log.txt there are at least 30 crashes. Now...

AFL++ stores crashes in OUTPUT/default/crashes, is it possible that you are not executing the testcases in this dir when measuring crashes, but only from the queue?

From what I'm understanding (correct me please) you extract the corpus tar.gz, the for AFL++ contains a directory struct of type corpus/default/{queue, crashes, hangs}, [here](https://github.com/google/fuzzbench/blob/master/experiment/measurer/measure_manager.py#L495), then you run libfuzzer merge...

I'm going to increase the mem limit and the timeout and update you then, my suggestion is also to exclude the hangs subdir to speedup the merge process.

[This](https://github.com/google/fuzzbench/blob/master/experiment/measurer/measure_manager.py#L545) seems a bug because it does not recurse the subdirs (I guess is should be os.walk instead of os.listdir)