2018-11-09 23:10:24 +00:00
|
|
|
homepage: "https://git-scm.com"
|
2020-03-10 18:08:01 +00:00
|
|
|
language: c++
|
2018-11-09 23:10:24 +00:00
|
|
|
primary_contact: "steadmon@google.com"
|
2020-09-02 23:39:19 +00:00
|
|
|
auto_ccs:
|
|
|
|
|
- "git-fuzz-reports@google.com"
|
2020-09-17 00:51:43 +00:00
|
|
|
- "emilyshaffer@google.com"
|
|
|
|
|
- "jonathantanmy@google.com"
|
|
|
|
|
- "jrn@google.com"
|
2022-08-01 10:05:13 +00:00
|
|
|
- "david@adalogics.com"
|
2020-12-10 05:52:40 +00:00
|
|
|
main_repo: 'https://github.com/git/git'
|
git: workaround new requirement to use common-main (#7818)
Due to upstream changes, the Git fuzzers must now link against
common-main.o; however, this breaks the build in two ways:
1) Linking with common-main.o causes main() to have multiple
definitions, one in common-main.o and one from the fuzzing engine.
2) To avoid #1, the Git Makefile specifically excludes common-main.o
from the fuzzer build rule.
To work around these issues, we can override FUZZ_CXXFLAGS (add
"-Wl,--allow-multiple-definition" to fix #1) and LIB_FUZZING_ENGINE (add
"common-main.o" to fix #2).
Once we can get a Makefile fix into Git's upstream, we can remove the
override for LIB_FUZZING_ENGINE.
However, this change causes `check_build` to fail for honggfuzz, and we
have not yet been able to diagnose the reason. So for now, we also need
to limit our engines to afl and libfuzzer.
2022-07-16 23:46:23 +00:00
|
|
|
|
|
|
|
|
# Disable honggfuzz due to undiagnosed build failures
|
|
|
|
|
fuzzing_engines:
|
|
|
|
|
- libfuzzer
|
|
|
|
|
- afl
|
