Enable DMP for system Chromium WebView on Android

base/allocator/allocator.gyp

Index: base/allocator/allocator.gyp
diff --git a/base/allocator/allocator.gyp b/base/allocator/allocator.gyp
index 4febed2533dfdbe87cb1efb360fe6dd2406711ee..ef98d09482bb71c03ef9767f37ecf46beb7a67d7 100644
--- a/base/allocator/allocator.gyp
+++ b/base/allocator/allocator.gyp
@@ -429,6 +429,11 @@
               '-Wl,-u_ZN15HeapLeakChecker12IgnoreObjectEPKv,-u_ZN15HeapLeakChecker14UnIgnoreObjectEPKv',
           ]},
         }],
+        # Need to distinguish a non-SDK build for Android WebView
+        # due to differences in C include files.
+        ['OS=="android" and android_webview_build==1', {
+          'defines': ['ANDROID_NON_SDK_BUILD'],
+        }],

[Dai Mikurube (NOT FULLTIME), 2013/07/15 16:48:05]

Hmm, sorry, my comment was confusing.

I wanted that the changes on tcmalloc/chromium can be eventually upstreamed to
the original gperftools. The difference between the original gperftools and
Chromium's branch should be minimum.

Are "SDK build" and "non-SDK build" generic build settings on Android, or
Chromium-specific?  I'm not sure on Android.

If they're generic, the best way is to use a stable condition without depending
on an external definition like ANDROID_NON_SDK_BUILD, or to import the
definition into gperftools' build configuration. (FYI, __NR_SYSCALL_BASE is
actually ok if it's a stable condition for past and future Android. I used
__ANDROID__ since it looked stable.)

If they're Chromium-specific, ANDROID_NON_SDK_BUILD definition is ok. The only
way is to accept some difference between the original gperftools and Chromium's
branch, and then minimize the difference.

         [ 'use_vtable_verify==1', {
           'cflags': [
             '-fvtable-verify=preinit',