Remove forced static_library build for Dr. Memory now that the tool

supports the debug MSVS libc dll.  Also disabled debug build inlining
and FPO to support increasing debug build optimization.

Re-add unit_tests to the "Windows Tests (DrMemory)" bot.  (The
unit_tests cannot be linked with static_library, which is why they
were removed from the bot.)

BUG=137180

R=rnk@chromium.org

Review URL: https://chromiumcodereview.appspot.com/10834341

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@151770 0039d316-1c4b-4281-b951-d872f2087c98

build/all.gyp

@@ -522,6 +522,7 @@
           'type': 'none',
           'dependencies': [
             '../base/base.gyp:base_unittests',
+            '../chrome/chrome.gyp:unit_tests',
             '../cloud_print/cloud_print.gyp:cloud_print_unittests',
             '../content/content.gyp:content_unittests',
             '../crypto/crypto.gyp:crypto_unittests',

build/common.gypi

@@ -1217,8 +1217,6 @@
       # TODO(rnk): Combine with tsan config to share the builder.
       # http://crbug.com/108155
       ['build_for_tool=="drmemory"', {
-        # DrMemory can't handle the debug CRT dll, so build static.
-        'component': 'static_library',
         # These runtime checks force initialization of stack vars which blocks
         # DrMemory's uninit detection.
         'win_debug_RuntimeChecks': '0',
@@ -1227,6 +1225,9 @@
         # Try to disable optimizations that mess up stacks in a release build.
         'win_release_InlineFunctionExpansion': '0',
         'win_release_OmitFramePointers': '0',
+        # Ditto for debug, to support bumping win_debug_Optimization.
+        'win_debug_InlineFunctionExpansion': 0,
+        'win_debug_OmitFramePointers': 0,
         # Keep the code under #ifndef NVALGRIND.
         'release_valgrind_build': 1,
       }],