diff options
author | csilvers <csilvers@6b5cf1ce-ec42-a296-1ba9-69fdba395a50> | 2011-01-19 21:37:15 +0000 |
---|---|---|
committer | csilvers <csilvers@6b5cf1ce-ec42-a296-1ba9-69fdba395a50> | 2011-01-19 21:37:15 +0000 |
commit | 3d77cbf7d569a7c7f0ce39a83f6c98da1718f1c4 (patch) | |
tree | 282bf9eac172415917c81a60ee6c93fdfc1ba625 /README | |
parent | a0a2ff3b493481ff52e4b4deec2fcc494756b64a (diff) | |
download | gperftools-3d77cbf7d569a7c7f0ce39a83f6c98da1718f1c4.tar.gz |
* Make kHideMask use all 64 bits (ppluzhnikov)
* Add new IsDebuggerAttached method (ppluzhnikov)
* Document some tricks for maybe getting perftools to work on OS X
* Redo file-top pprof commands (csilvers)
* Clean up pprof input-file handling (csilvers)
* 16-byte align debug allocs (jyasskin)
* Ignore JVM memory leakage in the heap checker (davidyu, kkurimoto)
* Better internal-function list for contentionz (ruemmler)
* mmap2 on i386 takes an off_t, not an off64_t (csilvers)
* Fix up fake-VDSO handling for unittest (ppluzhnikov)
* Don't try to check valgrind for windows (csilvers)
git-svn-id: http://gperftools.googlecode.com/svn/trunk@101 6b5cf1ce-ec42-a296-1ba9-69fdba395a50
Diffstat (limited to 'README')
-rw-r--r-- | README | 22 |
1 files changed, 22 insertions, 0 deletions
@@ -196,6 +196,28 @@ that error. To fix it, just comment out (or delete) the line in your config.h file before building. +OS X ISSUES +----------- + +You may need to set the environment variable DYLD_FORCE_FLAT_NAMESPACE +to use perftools with OS X. Because of how OS X does symbol binding, +libc routines will use libc malloc even when the binary is linked with +-ltcmalloc. This is not usually a problem, but becomes one if the +application is responsible for freeing that memory: the application +will use tcmalloc's free() to try to free memory allocated with libc's +malloc(), which will cause no end of confusion. + +One (or both) of these workaround may fix the problem: + DYLD_FORCE_FLAT_NAMESPACE=1 myapp + DYLD_INSERT_LIBRARIES=path/to/libtcmalloc.dylib myapp + +The best solution may depend on the version of OS X being used. +Neither solution is likely to work if you dlopen() libraries from +within your application. If you have any experience with this, we'd +appreciate you sharing it at + http://groups.google.com/group/google-perftools + + 64-BIT ISSUES ------------- |