[libfuzzer] Add fuzzer for FT_New_Memory_Face() from third_party/freetype2.

testing/libfuzzer/fuzzers/BUILD.gn

Index: testing/libfuzzer/fuzzers/BUILD.gn
diff --git a/testing/libfuzzer/fuzzers/BUILD.gn b/testing/libfuzzer/fuzzers/BUILD.gn
index 56a42579c2beab6f20ca1ca58bd0ad7400d4a2f1..35080b063349cefa6efa6aae728cd1cce7ca363f 100644
--- a/testing/libfuzzer/fuzzers/BUILD.gn
+++ b/testing/libfuzzer/fuzzers/BUILD.gn
@@ -323,3 +323,12 @@ fuzzer_test("libxml_xml_regexp_compile_fuzzer") {
   libfuzzer_options = "libxml_xml_regexp_compile_fuzzer.options"
   additional_configs = [ "//testing/libfuzzer:no_clusterfuzz" ]
 }
+
+fuzzer_test("third_party_ft_new_memory_face_fuzzer") {
+  sources = [
+    "ft_new_memory_face_fuzzer.cc",
+  ]
+  deps = [
+    "//third_party/freetype2",

[bungeman-chromium, 2016/03/09 18:34:35]

While this is the freetype we run the tests with, it isn't very interesting to
fuzz because  it's really old (it's the one in precise). It is unlikely that any
findings would be current.

[bungeman-chromium, 2016/03/09 18:49:26]

Just wanted to point out that running this against any of the targets in
Chromium is strictly less interesting that running against FreeType tip of tree
using their build system. We do try to keep up to date these days, but there is
a big difference between continuous and once a month or so.

+  ]
+}