Add a script to produce a syzygy-instrumented image of Chrome.dll

chrome/installer/mini_installer/chrome.release

Index: chrome/installer/mini_installer/chrome.release
diff --git a/chrome/installer/mini_installer/chrome.release b/chrome/installer/mini_installer/chrome.release
index 8658f4430c3a6271db05b13d907c6ee4d4acca76..2500c79274998baccd5c342de8fc4a9a2f7111fd 100644
--- a/chrome/installer/mini_installer/chrome.release
+++ b/chrome/installer/mini_installer/chrome.release
@@ -29,6 +29,8 @@ libGLESv2.dll: %(VersionDir)s\
 xinput1_3.dll: %(VersionDir)s\
 default_apps\*.crx: %(VersionDir)s\default_apps\
 default_apps\external_extensions.json: %(VersionDir)s\default_apps\
+asan_rtl.dll: %(VersionDir)s\
+logger.exe: %(ChromeDir)s\

[Roger McFarlane (Chromium), 2013/02/01 18:54:30]

I'm not sure we want to include the logger in the package. To do so would
further require (or at least benefit from) the inclusion of symsrv.dll as well.
That said, does this actually result in the logger being included?

[Sébastien Marchand, 2013/02/01 19:54:31]

It'll only include the logger if it finds it in the output directories (in the
case of SyzyAsan this means out\Release and out\Release\syzygy). 

So the general use-case for our users would be to run an instrumented version on
their machine, and if an error is found a minidump will be generated and send to
us ? We'll be able to get the Asan report with just the minidump, and the
matching version of chrome.dll/pdb ? In this case we should remove the logger
from this list.

And as we don't ship the PDB it's useless to include the logger....

 
 [HIDPI]
 chrome_200_percent.pak: %(VersionDir)s\