Reland of Add function to trace stack using frame pointers.

Reland of Add function to trace stack using frame pointers.

Original CL (1879073002) was reverted because it triggered several
use-of-uninitialized-value errors on Linux ChromeOS MSan bot. See
crbug.com/602701#c6 for details. Those errors are expected because
reading values from the stack outside of the function's frame is
essential to the process of unwinding.

This CL adds change to disable the unit test if MEMORY_SANITIZER is
defined. Additionally, this CL fixes unwinding on ARM by moving sp
adjustment several lines up.

Original issue's description:
> For memory-infra we need fast stack traces to implement allocation
> tracing (see https://goo.gl/DFoqfi). StackTrace class uses unwinding
> and is too slow. This change adds a function that uses frame pointers
> to walk the stack.
>
> The function supports x86, x64 and arm (but not thumb) architectures
> on POSIX platforms.

BUG=602701
Committed: https://crrev.com/79080da0203790b2e12ab36ab50f8a374aea8455
Cr-Commit-Position: refs/heads/master@{#389320}

[Dmitry Skiba, 2016-04-22 18:30:00]

Description was changed from

==========
Reland of Add function to trace stack using frame pointers.

Original CL (1879073002) was reverted because it triggered several
use-of-uninitialized-value errors on Linux ChromeOS MSan bot. See
crbug.com/602701#c6 for details. Those errors are expected because
reading values from the stack outside of the function's frame is
essential to the process of unwinding.

This CL adds change to disable the unit test if MEMORY_SANITIZER is
defined.

Original issue's description:
> For memory-infra we need fast stack traces to implement allocation
> tracing (see https://goo.gl/DFoqfi). StackTrace class uses unwinding
> and is too slow. This change adds a function that uses frame pointers
> to walk the stack.
>
> The function supports x86, x64 and arm (but not thumb) architectures
> on POSIX platforms.

BUG=602701
==========

to

==========
Reland of Add function to trace stack using frame pointers.

Original CL (1879073002) was reverted because it triggered several
use-of-uninitialized-value errors on Linux ChromeOS MSan bot. See
crbug.com/602701#c6 for details. Those errors are expected because
reading values from the stack outside of the function's frame is
essential to the process of unwinding.

This CL adds change to disable the unit test if MEMORY_SANITIZER is
defined. Additionally, this CL fixes unwinding on ARM by moving sp
adjustment several lines up.

Original issue's description:
> For memory-infra we need fast stack traces to implement allocation
> tracing (see https://goo.gl/DFoqfi). StackTrace class uses unwinding
> and is too slow. This change adds a function that uses frame pointers
> to walk the stack.
>
> The function supports x86, x64 and arm (but not thumb) architectures
> on POSIX platforms.

BUG=602701
==========

[Dmitry Skiba, 2016-04-22 18:48:22]

dskiba@google.com changed reviewers:
+ primiano@chromium.org, thakis@chromium.org

[Dmitry Skiba, 2016-04-22 18:48:23]

Guys, please review.

(This is what you get when you aggressively land un-LGTM'ed changes... MSan gods
get angry. But you find a bug in the proccess.)

[Nico, 2016-04-22 20:03:56]

lgtm

[Dmitry Skiba, 2016-04-22 22:55:56]

The CQ bit was checked by dskiba@google.com

[commit-bot: I haz the power, 2016-04-22 22:56:26]

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

[commit-bot: I haz the power, 2016-04-23 00:10:36]

Description was changed from

==========
Reland of Add function to trace stack using frame pointers.

Original CL (1879073002) was reverted because it triggered several
use-of-uninitialized-value errors on Linux ChromeOS MSan bot. See
crbug.com/602701#c6 for details. Those errors are expected because
reading values from the stack outside of the function's frame is
essential to the process of unwinding.

This CL adds change to disable the unit test if MEMORY_SANITIZER is
defined. Additionally, this CL fixes unwinding on ARM by moving sp
adjustment several lines up.

Original issue's description:
> For memory-infra we need fast stack traces to implement allocation
> tracing (see https://goo.gl/DFoqfi). StackTrace class uses unwinding
> and is too slow. This change adds a function that uses frame pointers
> to walk the stack.
>
> The function supports x86, x64 and arm (but not thumb) architectures
> on POSIX platforms.

BUG=602701
==========

to

==========
Reland of Add function to trace stack using frame pointers.

Original CL (1879073002) was reverted because it triggered several
use-of-uninitialized-value errors on Linux ChromeOS MSan bot. See
crbug.com/602701#c6 for details. Those errors are expected because
reading values from the stack outside of the function's frame is
essential to the process of unwinding.

This CL adds change to disable the unit test if MEMORY_SANITIZER is
defined. Additionally, this CL fixes unwinding on ARM by moving sp
adjustment several lines up.

Original issue's description:
> For memory-infra we need fast stack traces to implement allocation
> tracing (see https://goo.gl/DFoqfi). StackTrace class uses unwinding
> and is too slow. This change adds a function that uses frame pointers
> to walk the stack.
>
> The function supports x86, x64 and arm (but not thumb) architectures
> on POSIX platforms.

BUG=602701
==========

[commit-bot: I haz the power, 2016-04-23 00:10:36]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-04-23 00:12:39]

Description was changed from

==========
Reland of Add function to trace stack using frame pointers.

Original CL (1879073002) was reverted because it triggered several
use-of-uninitialized-value errors on Linux ChromeOS MSan bot. See
crbug.com/602701#c6 for details. Those errors are expected because
reading values from the stack outside of the function's frame is
essential to the process of unwinding.

This CL adds change to disable the unit test if MEMORY_SANITIZER is
defined. Additionally, this CL fixes unwinding on ARM by moving sp
adjustment several lines up.

Original issue's description:
> For memory-infra we need fast stack traces to implement allocation
> tracing (see https://goo.gl/DFoqfi). StackTrace class uses unwinding
> and is too slow. This change adds a function that uses frame pointers
> to walk the stack.
>
> The function supports x86, x64 and arm (but not thumb) architectures
> on POSIX platforms.

BUG=602701
==========

to

==========
Reland of Add function to trace stack using frame pointers.

Original CL (1879073002) was reverted because it triggered several
use-of-uninitialized-value errors on Linux ChromeOS MSan bot. See
crbug.com/602701#c6 for details. Those errors are expected because
reading values from the stack outside of the function's frame is
essential to the process of unwinding.

This CL adds change to disable the unit test if MEMORY_SANITIZER is
defined. Additionally, this CL fixes unwinding on ARM by moving sp
adjustment several lines up.

Original issue's description:
> For memory-infra we need fast stack traces to implement allocation
> tracing (see https://goo.gl/DFoqfi). StackTrace class uses unwinding
> and is too slow. This change adds a function that uses frame pointers
> to walk the stack.
>
> The function supports x86, x64 and arm (but not thumb) architectures
> on POSIX platforms.

BUG=602701

Committed: https://crrev.com/79080da0203790b2e12ab36ab50f8a374aea8455
Cr-Commit-Position: refs/heads/master@{#389320}
==========

[commit-bot: I haz the power, 2016-04-23 00:12:40]

Patchset 3 (id:??) landed as
https://crrev.com/79080da0203790b2e12ab36ab50f8a374aea8455
Cr-Commit-Position: refs/heads/master@{#389320}