Commit Graph

5 Commits

Author SHA1 Message Date
jonathanmetzman 3049c50d48
Migrate projects using -lFuzzingEngine to $LIB_FUZZING_ENGINE (#2325)
Migrate from -lFuzzingEngine to $LIB_FUZZING_ENGINE where possible and not causing breakage
2019-05-01 11:09:55 -04:00
Nelson Elhage 1e4d186ed3 libgit2: Let fuzzers user internal headers (#1875) 2018-10-15 13:54:48 +11:00
Patrick Steinhardt 90bdc6a32f [libgit2] Use upstreamed fuzzers (#1684)
To get the ball rolling more quickly, the download_refs fuzzer for
libgit2 was first implemented directly in oss-fuzz. But as we want to
ensure that we're not breaking fuzzers and thus at least build them as
part of our CI, the goal has been to upstream them into libgit2.

This commit removes the download_refs fuzzer and its corpus in favor of
using the upstreamed fuzzer. Furthermore, the build script is
generalized to automatically pick up new fuzzers named according to a
certain pattern, as we already added a second packfile fuzzer.
2018-08-03 07:20:21 -07:00
Patrick Steinhardt 7951fd64fd [libgit2] create build directory only if it doesn't exist yet (#1633)
Right now, we're always trying to create the project build directory,
even if it already exists. When building the fuzzer with an already
existing project directory, though, this may produce an error if the
build directory already exists. Fix this by adding the "-p" flag to
mkdir(1), which will not produce an error if the target already exists.
2018-07-19 07:10:40 -07:00
Nelson Elhage c0661eefc4 Add a fuzzer for libgit2 (#1604)
* Add a libgit2 fuzzer for the `git fetch` client

* Use a fresh remote each time

* Build fewer things, use fewer deps

* no ssh, either

* Add a corpus with one file.

Slightly tweaked network dump of a `git clone` on a tiny repo.

* auto_ccs is a list

* Rename the fuzzer

* only email in project.yaml

* Use `master`

I had left in a `-b oss-fuzz` from testing off my fork
2018-07-13 08:13:05 -07:00