Update the tcmalloc vendor branch to r144 (gperftools 2.0).

third_party/tcmalloc/vendor/INSTALL

 Copyright 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software
 Foundation, Inc.
 
    This file is free documentation; the Free Software Foundation gives
 unlimited permission to copy, distribute and modify it.
 
 
 Perftools-Specific Install Notes
 ================================
 
 *** NOTE FOR 64-BIT LINUX SYSTEMS
 
 The glibc built-in stack-unwinder on 64-bit systems has some problems
 with the perftools libraries.  (In particular, the cpu/heap profiler
 may be in the middle of malloc, holding some malloc-related locks when
 they invoke the stack unwinder.  The built-in stack unwinder may call
 malloc recursively, which may require the thread to acquire a lock it
 already holds: deadlock.)
 
 For that reason, if you use a 64-bit system, we strongly recommend you
-install libunwind before trying to configure or install google
-perftools.  libunwind can be found at
+install libunwind before trying to configure or install gperftools.
+libunwind can be found at
 
    http://download.savannah.gnu.org/releases/libunwind/libunwind-0.99-beta.tar.gz
 
 Even if you already have libunwind installed, you should check the
 version.  Versions older than this will not work properly; too-new
 versions introduce new code that does not work well with perftools
 (because libunwind can call malloc, which will lead to deadlock).
 
-CAUTION: if you install libunwind from the url above, be aware that
-you may have trouble if you try to statically link your binary with
-perftools: that is, if you link with 'gcc -static -lgcc_eh ...'.  This
-is because both libunwind and libgcc implement the same C++ exception
-handling APIs, but they implement them differently on some platforms.
-This is not likely to be a problem on ia64, but may be on x86-64.
+There have been reports of crashes with libunwind 0.99 (see
+http://code.google.com/p/gperftools/issues/detail?id=374).
+Alternately, you can use a more recent libunwind (e.g. 1.0.1) at the
+cost of adding a bit of boilerplate to your code.  For details, see
+http://groups.google.com/group/google-perftools/msg/2686d9f24ac4365f
 
-Also, if you link binaries statically, make sure that you add 
--Wl,--eh-frame-hdr to your linker options. This is required so that
-libunwind can find the information generated by the compiler required
-for stack unwinding.
+   CAUTION: if you install libunwind from the url above, be aware that
+   you may have trouble if you try to statically link your binary with
+   perftools: that is, if you link with 'gcc -static -lgcc_eh ...'.
+   This is because both libunwind and libgcc implement the same C++
+   exception handling APIs, but they implement them differently on
+   some platforms.  This is not likely to be a problem on ia64, but
+   may be on x86-64.
 
-Using -static is rare, though, so unless you know this will affect you
-it probably won't.
+   Also, if you link binaries statically, make sure that you add
+   -Wl,--eh-frame-hdr to your linker options. This is required so that
+   libunwind can find the information generated by the compiler
+   required for stack unwinding.
+
+   Using -static is rare, though, so unless you know this will affect
+   you it probably won't.
 
 If you cannot or do not wish to install libunwind, you can still try
 to use the built-in stack unwinder.  The built-in stack unwinder
 requires that your application, the tcmalloc library, and system
 libraries like libc, all be compiled with a frame pointer.  This is
 *not* the default for x86-64.
 
 If you are on x86-64 system, know that you have a set of system
 libraries with frame-pointers enabled, and compile all your
 applications with -fno-omit-frame-pointer, then you can enable the
@@ skipping 75 matching lines @@
 asking for trouble in any case: some data will be allocated with one
 malloc, some with another.  If, for some reason, you *do* need to use
 dlopen on tcmalloc, the easiest way is to use a version of tcmalloc
 with TLS turned off; see the ___tls_get_addr note above.
 
 
 *** COMPILING ON NON-LINUX SYSTEMS
 
 Perftools has been tested on the following systems:
    FreeBSD 6.0 (x86)
+   FreeBSD 8.1 (x86_64)
+   Linux CentOS 5.5 (x86_64)
+   Linux Debian 4.0 (PPC)
+   Linux Debian 5.0 (x86)
    Linux Fedora Core 3 (x86)
    Linux Fedora Core 4 (x86)
    Linux Fedora Core 5 (x86)
    Linux Fedora Core 6 (x86)
+   Linux Fedora Core 13 (x86_64)
+   Linux Fedora Core 14 (x86_64)
+   Linux RedHat 9 (x86)
+   Linux Slackware 13 (x86_64)
    Linux Ubuntu 6.06.1 (x86)
    Linux Ubuntu 6.06.1 (x86_64)
-   Linux RedHat 9 (x86)
-   Linux Debian 4.0 (PPC)
+   Linux Ubuntu 10.04 (x86)
+   Linux Ubuntu 10.10 (x86_64)
    Mac OS X 10.3.9 (Panther) (PowerPC)
    Mac OS X 10.4.8 (Tiger) (PowerPC)
    Mac OS X 10.4.8 (Tiger) (x86)
    Mac OS X 10.5 (Leopard) (x86)
-   Solaris 10 (x86)
-   Windows XP, Visual Studio 2003 (VC++ 7) (x86)
+   Mac OS X 10.6 (Snow Leopard) (x86)
+   Solaris 10 (x86_64)
+   Windows XP, Visual Studio 2003 (VC++ 7.1) (x86)
    Windows XP, Visual Studio 2005 (VC++ 8) (x86)
+   Windows XP, Visual Studio 2005 (VC++ 9) (x86)
+   Windows XP, Visual Studio 2005 (VC++ 10) (x86)
    Windows XP, MinGW 5.1.3 (x86)
    Windows XP, Cygwin 5.1 (x86)
 
 It works in its full generality on the Linux systems
 tested (though see 64-bit notes above).  Portions of perftools work on
 the other systems.  The basic memory-allocation library,
 tcmalloc_minimal, works on all systems.  The cpu-profiler also works
 fairly widely.  However, the heap-profiler and heap-checker are not
 yet as widely supported.  In general, the 'configure' script will
 detect what OS you are building for, and only build the components
@@ skipping 87 matching lines @@
    % PATH=${PATH}:/usr/sfw/bin/:/usr/ccs/bin make [...]
 
    Again, the binaries and libraries that successfully build are
    exactly the same as for FreeBSD.  (However, while libprofiler.so can
    be used to generate profiles, pprof is not very successful at
    reading them -- necessary helper programs like nm don't seem
    to be installed by default on Solaris, or perhaps are only
    installed as part of the Sun C++ compiler package.)  See that
    section for a list of binaries, and instructions on building them.
 
-** Windows:
+** Windows  (MSVC, Cygwin, and MinGW):
 
    Work on Windows is rather preliminary: we haven't found a good way
    to get stack traces in release mode on windows (that is, when FPO
    is enabled), so the heap profiling may not be reliable in that
    case.  Also, heap-checking and CPU profiling do not yet work at
    all.  But as in other ports, the basic tcmalloc library
    functionality, overriding malloc and new and such (and even
    windows-specific functions like _aligned_malloc!), is working fine,
-   at least with VC++ 7.1 (Visual Studio 2003) and VC++ 8.0
-   (Visual Studio 2005), in both debug and release modes.  See
-   README.windows for instructions on how to install on Windows using
-   Visual Studio.
+   at least with VC++ 7.1 (Visual Studio 2003) through VC++ 10.0,
+   in both debug and release modes.  See README.windows for
+   instructions on how to install on Windows using Visual Studio.
 
    Cygwin can compile some but not all of perftools.  Furthermore,
    there is a problem with exception-unwinding in cygwin (it can call
    malloc, which can call the exception-unwinding-setup code, which
    can lead to an infinite loop).  I've comitted a workaround to the
    exception unwinding problem, but it only works in debug mode and
    when statically linking in tcmalloc.  I hope to have a more proper
    fix in a later release.  To configure under cygwin, run
 
       ./configure --disable-shared CXXFLAGS=-g && make
@@ skipping 228 matching lines @@
      Do not print messages saying which checks are being made.  To
      suppress all normal output, redirect it to `/dev/null' (any error
      messages will still be shown).
 
 `--srcdir=DIR'
      Look for the package's source code in directory DIR.  Usually
      `configure' can determine that directory automatically.
 
 `configure' also accepts some other, not widely useful, options.  Run
 `configure --help' for more details.