Revert of [tracing] Add native allocation tracing mode.

Revert of [tracing] Add native allocation tracing mode. (patchset #15 id:270001 of https://codereview.chromium.org/1839503002/ )

Reason for revert:
Appears to have caused a compile error on https://build.chromium.org/p/chromium/builders/Win%20x64/builds/92.

Original issue's description:
> [tracing] Add native allocation tracing mode.
>
> This change adds 'native' mode to '--enable-heap-profiling' option. When
> started with '--enable-heap-profiling=native' Chrome will keep native
> (real) stack traces for all live allocations. These native stack traces
> are then dumped to a trace file if 'memory-infra' category is enabled.
> Stack traces are dumped unsymbolized (for performance reasons), and there
> is a script (third_party/catapult/tracing/bin/symbolize_trace) that
> symbolizes all stack traces in a given trace file.
>
> Design document: https://goo.gl/DFoqfi
>
> Note: native stack tracing relies on frame pointers. You'll need to use
> either debug or a profiling release build (enable_profiling = true).
>
> Note: for now this all works on Linux @ x86/x64 only.
>
> BUG=602701
>
> Committed: https://crrev.com/5a05938adaabf413a40f1e0dfec3d1e4c683693a
> Cr-Commit-Position: refs/heads/master@{#389500}

TBR=primiano@chromium.org,perezju@chromium.org,ssid@chromium.org,mark@chromium.org,dskiba@google.com
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=602701
Committed: https://crrev.com/2a03e86fcfb6f831ef8658cbd360f54bb5ace62e
Cr-Commit-Position: refs/heads/master@{#389507}

[Charlie Reis, 2016-04-25 17:12:05]

Created Revert of [tracing] Add native allocation tracing mode.

[commit-bot: I haz the power, 2016-04-25 17:12:35]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1916033002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1916033002/1

[commit-bot: I haz the power, 2016-04-25 17:13:17]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-04-25 17:14:37]

Description was changed from

==========
Revert of [tracing] Add native allocation tracing mode. (patchset #15 id:270001
of https://codereview.chromium.org/1839503002/ )

Reason for revert:
Appears to have caused a compile error on
https://build.chromium.org/p/chromium/builders/Win%20x64/builds/92.

Original issue's description:
> [tracing] Add native allocation tracing mode.
> 
> This change adds 'native' mode to '--enable-heap-profiling' option. When
> started with '--enable-heap-profiling=native' Chrome will keep native
> (real) stack traces for all live allocations. These native stack traces
> are then dumped to a trace file if 'memory-infra' category is enabled.
> Stack traces are dumped unsymbolized (for performance reasons), and there
> is a script (third_party/catapult/tracing/bin/symbolize_trace) that
> symbolizes all stack traces in a given trace file.
> 
> Design document: https://goo.gl/DFoqfi
> 
> Note: native stack tracing relies on frame pointers. You'll need to use
> either debug or a profiling release build (enable_profiling = true).
> 
> Note: for now this all works on Linux @ x86/x64 only.
> 
> BUG=602701
> 
> Committed: https://crrev.com/5a05938adaabf413a40f1e0dfec3d1e4c683693a
> Cr-Commit-Position: refs/heads/master@{#389500}

TBR=primiano@chromium.org,perezju@chromium.org,ssid@chromium.org,mark@chromiu...
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=602701
==========

to

==========
Revert of [tracing] Add native allocation tracing mode. (patchset #15 id:270001
of https://codereview.chromium.org/1839503002/ )

Reason for revert:
Appears to have caused a compile error on
https://build.chromium.org/p/chromium/builders/Win%20x64/builds/92.

Original issue's description:
> [tracing] Add native allocation tracing mode.
>
> This change adds 'native' mode to '--enable-heap-profiling' option. When
> started with '--enable-heap-profiling=native' Chrome will keep native
> (real) stack traces for all live allocations. These native stack traces
> are then dumped to a trace file if 'memory-infra' category is enabled.
> Stack traces are dumped unsymbolized (for performance reasons), and there
> is a script (third_party/catapult/tracing/bin/symbolize_trace) that
> symbolizes all stack traces in a given trace file.
>
> Design document: https://goo.gl/DFoqfi
>
> Note: native stack tracing relies on frame pointers. You'll need to use
> either debug or a profiling release build (enable_profiling = true).
>
> Note: for now this all works on Linux @ x86/x64 only.
>
> BUG=602701
>
> Committed: https://crrev.com/5a05938adaabf413a40f1e0dfec3d1e4c683693a
> Cr-Commit-Position: refs/heads/master@{#389500}

TBR=primiano@chromium.org,perezju@chromium.org,ssid@chromium.org,mark@chromiu...
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=602701

Committed: https://crrev.com/2a03e86fcfb6f831ef8658cbd360f54bb5ace62e
Cr-Commit-Position: refs/heads/master@{#389507}
==========

[commit-bot: I haz the power, 2016-04-25 17:14:37]

Patchset 1 (id:??) landed as
https://crrev.com/2a03e86fcfb6f831ef8658cbd360f54bb5ace62e
Cr-Commit-Position: refs/heads/master@{#389507}