update deep-memory-profiler policy for stlport

update deep-memory-profiler policy for stlport

1. android uses stlport in ndk library,
   and this library does not have same demangled name with libc++ stl.
   so we can get rid of tc-std-* from android policies.
2. tc-stl-node and tc-stl-vector have same stackstrace.
   so I changed std-node to std-other to hook all other std mallocs.
3. tc-toplevel-string regex has changed.

Bug=None
NOTRY=True

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=284633

[JungJik, 2014-07-15 12:38:21]

Please take a look :)

[Dai Mikurube (NOT FULLTIME), 2014-07-16 05:59:19]

lgtm. Thanks!

[JungJik, 2014-07-16 11:13:58]

On 2014/07/16 05:59:19, Dai Mikurube wrote:
> lgtm. Thanks!

thanks for lgtm.
however I misunderstood about stl library.
because ndk stl library and libc++ stl libary are implemented differently.
so demangle symbol-name is different. I will update this patch again.
sorry for inconvenience.

[JungJik, 2014-07-18 11:32:07]

On 2014/07/16 11:13:58, JungJik wrote:
> On 2014/07/16 05:59:19, Dai Mikurube wrote:
> > lgtm. Thanks!
> 
> thanks for lgtm.
> however I misunderstood about stl library.
> because ndk stl library and libc++ stl libary are implemented differently.
> so demangle symbol-name is different. I will update this patch again.
> sorry for inconvenience.

@Dai Mikurube: when you are free, PTAL again :)

[Dai Mikurube (NOT FULLTIME), 2014-07-22 02:56:33]

Still lgtm. Thanks!

[JungJik, 2014-07-22 05:00:04]

On 2014/07/22 02:56:33, Dai Mikurube wrote:
> Still lgtm. Thanks!

Thanks for lgtm :). now dmp can see all tc values. thanks again.

[JungJik, 2014-07-22 05:00:09]

The CQ bit was checked by jungjik.lee@samsung.com

[commit-bot: I haz the power, 2014-07-22 05:01:03]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/jungjik.lee@samsung.com/387313003/60001

[commit-bot: I haz the power, 2014-07-22 05:04:02]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-07-22 05:04:03]

Failed to apply patch for tools/deep_memory_profiler/policy.l2.json:
While running patch -p1 --forward --force --no-backup-if-mismatch;
  patching file tools/deep_memory_profiler/policy.l2.json
  Hunk #1 FAILED at 317.
  1 out of 2 hunks FAILED -- saving rejects to file
tools/deep_memory_profiler/policy.l2.json.rej

Patch:       tools/deep_memory_profiler/policy.l2.json
Index: tools/deep_memory_profiler/policy.l2.json
diff --git a/tools/deep_memory_profiler/policy.l2.json
b/tools/deep_memory_profiler/policy.l2.json
index
a88223e0350abf5f95389eeb8ec51767c3eb0328..d4c77e865cd49b205b79637a5b1735448358c1ef
100644
--- a/tools/deep_memory_profiler/policy.l2.json
+++ b/tools/deep_memory_profiler/policy.l2.json
@@ -317,7 +317,7 @@
     },
     {
       "name": "tc-webcore-resource",
-      "stacktrace": ".*WebCore::ResourceFetcher::requestResource .*", 
+      "stacktrace": ".*WebCore::ResourceFetcher::requestResource .*",
       "allocator": "malloc"
     },
     {
@@ -442,7 +442,7 @@
     },
     {
       "name": "tc-toplevel-string",
-      "stacktrace": "std::basic_string::_Rep::_S_create",
+      "stacktrace": ".*::allocate std::basic_string::_Rep::_S_create.*",
       "allocator": "malloc"
     },
     {

[JungJik, 2014-07-22 05:27:40]

On 2014/07/22 05:04:03, I haz the power (commit-bot) wrote:
> Failed to apply patch for tools/deep_memory_profiler/policy.l2.json:
> While running patch -p1 --forward --force --no-backup-if-mismatch;
>   patching file tools/deep_memory_profiler/policy.l2.json
>   Hunk #1 FAILED at 317.
>   1 out of 2 hunks FAILED -- saving rejects to file
> tools/deep_memory_profiler/policy.l2.json.rej
> 
> Patch:       tools/deep_memory_profiler/policy.l2.json
> Index: tools/deep_memory_profiler/policy.l2.json
> diff --git a/tools/deep_memory_profiler/policy.l2.json
> b/tools/deep_memory_profiler/policy.l2.json
> index
>
a88223e0350abf5f95389eeb8ec51767c3eb0328..d4c77e865cd49b205b79637a5b1735448358c1ef
> 100644
> --- a/tools/deep_memory_profiler/policy.l2.json
> +++ b/tools/deep_memory_profiler/policy.l2.json
> @@ -317,7 +317,7 @@
>      },
>      {
>        "name": "tc-webcore-resource",
> -      "stacktrace": ".*WebCore::ResourceFetcher::requestResource .*", 
> +      "stacktrace": ".*WebCore::ResourceFetcher::requestResource .*",
>        "allocator": "malloc"
>      },
>      {
> @@ -442,7 +442,7 @@
>      },
>      {
>        "name": "tc-toplevel-string",
> -      "stacktrace": "std::basic_string::_Rep::_S_create",
> +      "stacktrace": ".*::allocate std::basic_string::_Rep::_S_create.*",
>        "allocator": "malloc"
>      },
>      {

nothing has been changed. just removing a white-space causes this conflict.
I'll attempt to commit again.

[JungJik, 2014-07-22 05:27:49]

The CQ bit was checked by jungjik.lee@samsung.com

[commit-bot: I haz the power, 2014-07-22 05:28:56]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/jungjik.lee@samsung.com/387313003/80001

[commit-bot: I haz the power, 2014-07-22 05:30:06]

Change committed as 284633