issue deprecation warning on use of google/ headers
added tc_malloc_skip_new_handler

This is port of corresponding chromium change at:
https://codereview.chromium.org/55333002/

Basic idea is that sometimes apps that use tc_set_new_mode in order to
have C++ out-of-memory handler catch OOMs in malloc, need to invoke
usual malloc that returns 0 on OOM.

That new API is exactly for that. It'll always return NULL on OOM even
if tc_new_mode is set to true.
issue-614: use tc_memalign in ReallocAfterMemalloc test

Because some OSes lack plain memalign. And we really need to test our
implementation which is always available via tc_malloc.
Fixed the use of addr2line to discover the separator symbol.

In systems where addr2line has a version greater than 2.22 pprof fails
in discover the separator symbol (_fini). This patch identifies if
addr2line can find the symbol, otherwise pprof uses objdump to recover
a address that addr2line's newer versions can recognize as the separator
function.
Fixed the way that pprof packed profile data in BE.

pprof was writing profile data in a way that only works for little-endian
files, this patch verifies if the system is big-endian and writes packed
data correctly.
Fixed issues with heap checker on PPC64 LE.

Fixed the wrapper for the syscall sys_clone and the test for heap
checker on PPC64 LE. Both use the ODP structure, which is only
used on BE architectures.
VDSOsupport cleanup

This patch cleans up unused VDSO getcpu racking from VDSOsupport class,
since the code is not used anywhere in gperftools and symbol name is not
architecture independent.
PowerPC: stacktrace function refactor and fixes

This patch fixes the stacktrace creating when the function is
interrupted by a signal. For Linux, the vDSO signal trampoline symbol is
compared against LR from stack backchain and handled different in that
case (since the signal trampoline layout a different stack frame).

Because of this extensive change the PowerPC stacktrace code has now
been refactored to split in Linux and Darwin specific codes.
don't enable backtrace() for stacktrace capturing by default

Because we don't yet have a treatment for deadlocks that are caused by
(recursive) use of malloc from within that facility.
issue-610: introduced TCMallocGetenvSafe

This is version of GetenvBeforeMain that's available to C code.
issue-610: made dynamic_annotations.c use TCMallocGetenvSafe
issue-610: use TCMallocGetenvSafe from inside malloc

Instead of plain getenv. So that windows getenv implementation that
may call malloc does not deadlock.
updated NEWS for 2.2rc
bumped version to 2.1.90
issue-620: windows dll patching: fixed delete of old stub code

After code for issue 359 was applied PreamblePatcher started using
it's own code to manage memory of stub code fragments. It's not using
new[] anymore. And it automatically frees stub code memory on
Unpatch.

Clearly, author of that code forgot to remote that no more needed
delete call. With that delete call we end up trying to free memory
that was never allocated with any of known allocators and crash.
updated NEWS for 2.2
bumped version to 2.2