Instantiate a Kasko reporter inside the Chrome watcher process, when SyzyASAN instrumented.

chrome/chrome_exe.gypi

Index: chrome/chrome_exe.gypi
diff --git a/chrome/chrome_exe.gypi b/chrome/chrome_exe.gypi
index 46c84f9883347a301f2fc14deafaf3a2e2d448b3..ec8b03252d80a5c0185d8a8624b806d7a438a07b 100644
--- a/chrome/chrome_exe.gypi
+++ b/chrome/chrome_exe.gypi
@@ -109,6 +109,11 @@
             '../components/components.gyp:browser_watcher_client',
           ],
         }],
+        ['syzyasan==1', {
+          'dependencies': [
+            'copy_kasko_dlls',
+          ],
+        }],
         ['OS == "android"', {
           # Don't put the 'chrome' target in 'all' on android
           'suppress_wildcard': 1,
@@ -698,5 +703,31 @@
         },
       ],
     }],
+    ['syzyasan==1', {
+      'variables': {
+        'kasko_exe_dir': '<(DEPTH)/third_party/kasko',
+      },
+      # Copy the Kasko runtime to the build output directory so that it can be
+      # found when running from the build directory.
+      'targets': [
+        {
+          'target_name': 'copy_kasko_dlls',
+          'type': 'none',
+          'outputs': [
+            '<(PRODUCT_DIR)/kasko.dll',
+            '<(PRODUCT_DIR)/kasko.dll.pdb',

[cpu_(ooo_6.6-7.5), 2015/02/05 18:46:43]

wait, what is this part? 

[erikwright (departed), 2015/02/05 18:48:26]

The kasko build artifacts are retrieved via DEPS to thirdparty/kasko.

In this CL we link to them from chrome_watcher.dll.

In order to run the watcher process on a dev machine those DLLs need to be in
out/Debug (for example).

+          ],
+          'copies': [
+            {
+              'destination': '<(PRODUCT_DIR)',
+              'files': [
+                '<(kasko_exe_dir)/kasko.dll',
+                '<(kasko_exe_dir)/kasko.dll.pdb',
+              ],
+            },
+          ],
+        },
+      ],
+    }],
   ],
 }