diff options
author | chappedm@gmail.com <chappedm@gmail.com@6b5cf1ce-ec42-a296-1ba9-69fdba395a50> | 2012-09-18 00:00:20 +0000 |
---|---|---|
committer | chappedm@gmail.com <chappedm@gmail.com@6b5cf1ce-ec42-a296-1ba9-69fdba395a50> | 2012-09-18 00:00:20 +0000 |
commit | fa0209f261c5e065d523bb1858f84fd91eb2f39a (patch) | |
tree | ce4ff1c7da95243acddc721037a30b2029315d5c /src/heap-checker.cc | |
parent | cd723b43ff783a05321f0c0ba79a82494185b23c (diff) | |
download | gperftools-fa0209f261c5e065d523bb1858f84fd91eb2f39a.tar.gz |
issue-437 Fixed issues related to new glibc shipped with Ubuntu 10.10
1. ptrace permissions were modifed to be a bit more strict which required
us to programatically set the permissions while syncing up to the profiling
thread.
2. Order of destructors registered with atexit changed which was casuing us to
miss generating the backtrace when heap checker was finished. Seems that we
initially fixed this for FreeBSD and now linux has changed their behaviour
to be the same. We are now a bit stricter on the rules here accross all
platforms.
git-svn-id: http://gperftools.googlecode.com/svn/trunk@152 6b5cf1ce-ec42-a296-1ba9-69fdba395a50
Diffstat (limited to 'src/heap-checker.cc')
-rw-r--r-- | src/heap-checker.cc | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/heap-checker.cc b/src/heap-checker.cc index 5967b02..f55f356 100644 --- a/src/heap-checker.cc +++ b/src/heap-checker.cc @@ -2025,9 +2025,9 @@ void HeapLeakChecker_InternalInitStart() { // at the right time, on FreeBSD we always check after, even in the // less strict modes. This just means FreeBSD is always a bit // stricter in its checking than other OSes. -#ifdef __FreeBSD__ + // This now appears to be the case in other OSes as well; + // so always check afterwards. FLAGS_heap_check_after_destructors = true; -#endif { SpinLockHolder l(&heap_checker_lock); RAW_DCHECK(heap_checker_pid == getpid(), ""); |