Add LLVM fuzzer: Skia color space and color transform

testing/libfuzzer/fuzzers/BUILD.gn

 # Copyright 2015 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 # Individual libfuzzer tests that didn't find their home yet.
 
 import("//build/config/features.gni")
 import("//media/media_options.gni")
 import("//testing/libfuzzer/fuzzer_test.gni")
 
@@ skipping 402 matching lines @@
     "//base",
     "//skia",
   ]
   libfuzzer_options = [ "max_len=512" ]
   if (is_debug) {
     # Disabled due to crashing on SkASSERT (crbug.com/642750, crbug.com/643275).
     additional_configs = [ "//testing/libfuzzer:no_clusterfuzz" ]
   }
 }
 
+fuzzer_test("skia_color_space_fuzzer") {

[mmoroz, 2017/04/04 13:43:06]

Could you please move both the source code and the GN target to
third_party/skia/ ? I know that we have several fuzz targets for skia here
(https://cs.chromium.org/search/?q=file:skia.*+file:%5Esrc/testing/libfuzzer/f...),
but this is bad and we actually should move them to the skia project directory
as well.

[Noel Gordon, 2017/04/05 14:14:07]

Don't really work on Skia myself.

I know that we have several fuzz targets for skia here
Noticed there were a few skia fuzzer targets in the current BUILD file too.  So
that was a bit confusing to me, but perhaps another bug could move them all into
Skia.

Currently I want to share/use the color_space_data.h use another fuzzer I'm
building (for qcms which has nothing to do with skia), so for now I'd like to do
that. Where these fuzzers should eventually end up living is a good question
though, but not one I'm gonna tackle.  Perhaps after the fuzzers are built, we
can decide on that, as a subject of another bug.

[scroggo_chromium, 2017/04/05 21:02:47]

+1. FWIW, I do not think it would make sense to put the fuzzers in
third_party/skia, which is its own independent repository, since they depend on
other Chromium code. Code inside the Skia repository should be runnable outside
of Chromium. If this is not a good place for them, maybe src/skia is better?

Skia has its own fuzzers though, and I wouldn't be opposed to adding a fuzzer in
Skia which uses Skia's infrastructure. But it would be nice to be able to reuse
for other fuzzers as well.

[mmoroz, 2017/04/06 08:26:37]

Makes sense. Thanks for the explanation!

+  sources = [
+    "color_space_data.h",
+    "skia_color_space_fuzzer.cc",
+  ]
+  deps = [
+    "//base",
+    "//skia",
+  ]
+  dict = "dicts/icc.dict"
+  libfuzzer_options = [ "max_len=4194304" ]
+}
+
 fuzzer_test("prtime_fuzzer") {
   sources = [
     "prtime_fuzzer.cc",
   ]
   deps = [
     "//base",
   ]
   dict = "dicts/prtime.dict"
   libfuzzer_options = [ "max_len=1024" ]
 }
@@ skipping 16 matching lines @@
 }
 
 fuzzer_test("hash_fuzzer") {
   sources = [
     "hash_fuzzer.cc",
   ]
   deps = [
     "//base",
   ]
 }