-
Notifications
You must be signed in to change notification settings - Fork 257
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
afl++ build is broken on openssl_x509 #110
Comments
I think #115 is why this wasn't caught by CI |
Super strange, seems that afl-llvm-rt is not linked in the test. |
This can be fixed by skipping the check of |
I fixed it in the dev branch https://github.com/AFLplusplus/AFLplusplus/tree/dev with the solution proposed by @alifahmed . Waiting travis, then I'll merge it and update fuzzbench. |
Some targets needs to include afl-llvm-rt.o not only when linking, see google/fuzzbench#110. This change seems to not break nothing in AFL++.
Some targets needs to include afl-llvm-rt.o not only when linking, see google/fuzzbench#110. This change seems to not break nothing in AFL++.
* Remove dislocator from AFL++ One of the possible reasons of the decrement in performance of AFL++ in the lastest report is due to the missing AFL_ALIGNED_ALLOC env var. Without this variable, dislocator's malloc does not ensure that the returned address is aligned to max_aligned_t (as required by posix) but it is able, in this way, to catch more bugs. Many applications checks for this alignment and this may cause an early exit in the application (and so a low coverage). I completely remove dislocator to better understand what is happening in the next run of the experiments. * update AFL++ to fix #110 * afl++ cmplog * fix afl++ schedules flags error * unification of aflplusplus confs * update fuzzers.yml * make presubmit happy * add marc changes from #229 * presubmit * add also ngram2/4 * runner for cmplog * update commit * prepare new features * new variants * add support for ngram5 * add ctx variants * format * less lint more fire * seriously? one instead of two spaces is an issue? * add lto variant * update checkout * fix build lines * formatting * libfuzzer valueprofiles variant * formatting * formatting * remove old afl++ variants * update git * add afl++ variants * final afl++ variants * remove valuprofile and old symlink * fix laf-intel crash * update commit * fix for older llvm versions * fix bug in laf-intel for sqlite3 testcase * switch afl++ variants * remove LTO * fix fuckup in main fuzzer.py * update git * LTO submit * lto update * copy llvm11 c++ libs to targets * fix LTO and add 2nd LTO variant * remove 2 fuzzer variants to make space for LTO * LTO compiles curl target now, ensure flags are empty * fix tcpdump benchmark * jsoncpp needs a dynamic map too :-( * build and run all benchmarks * switch to tracepcguard * Revert "switch to tracepcguard" This reverts commit 782f555. * switch from instrim to tracepcguard * fix a fuzzer * fix formatting * remove temporary fuzzers * fix generate report document * fix report document, add report alternative * remove report changes * remove report changes * next variants * Revert "next variants" This reverts commit c551d90. * add new variants * nitpicks * remove fuzzer variants * remove variants from fuzzer.yaml * add optimal variant * formatting * fix builds * more build fixes * more build fixes * more build fixes * more build fixes * fix builds * various fixes and enhancements * formatting * formatting * fix. too tired * fix. too tired * add splitting floats to laf * enable lto for the relevant targets again after fixing bugs in laf+cmplog * freetype2 needs dynamic map * fix target compilation * fix target compilation * final touches for now * done performance tuning * add shmem variant Co-authored-by: Andrea Fioraldi <andreafioraldi@gmail.com> Co-authored-by: root <root@localhost.localdomain>
CC @andreafioraldi
Similar to #107 CI successfully built openssl_x509 with AFL++ but failed to do so on 2020-03-11.
The build fails with this error:
I will try to investigate the fix for this as well as if there is a way to make CI more likely to catch failures that happen in production.
The text was updated successfully, but these errors were encountered: