Type profiler by intercepting 'new' and 'delete' expressions.

base/allocator/type_profiler_control.h

Index: base/allocator/type_profiler_control.h
diff --git a/base/allocator/type_profiler_control.h b/base/allocator/type_profiler_control.h
new file mode 100644
index 0000000000000000000000000000000000000000..048a733e31d57cf956cbcc636195b40ca89407e5
--- /dev/null
+++ b/base/allocator/type_profiler_control.h
@@ -0,0 +1,32 @@
+// Copyright 2012 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef BASE_ALLOCATOR_TYPE_PROFILER_CONTROL_H_
+#define BASE_ALLOCATOR_TYPE_PROFILER_CONTROL_H_
+
+#include "base/gtest_prod_util.h"
+
+namespace base {
+namespace type_profiler {
+
+class Controller {
+ public:
+  static void Stop();
+  static bool IsProfiling();
+
+ private:
+  friend class TypeProfilerTest;
+  FRIEND_TEST_ALL_PREFIXES(TypeProfilerTest,

[Ryan Sleevi, 2012/09/13 09:13:25]

If you've friended TypeProfilerTest, you do not need to FRIEND_TEST_ALL_PREFIXES

The two are (generally) mutually exclusive. If you friend a class (really, a
test fixture), then you can access private/protected members. However, note that
all unit tests will be subclasses of that fixture, ergo they will not inherit
the friend-edness. To work around that, you have to use protected helper method
*on the fixture* to allow individual tests to access.

However, when you only have one or two tests, it's often easier and cleaner to
directly friend the test, rather than go through all that. Since you only have a
single test, remove the "friend class TypeProfilerTest", and the right thing
will happen (only TestProfileNewWithoutProfiledDelete will be friended)

[Dai Mikurube (NOT FULLTIME), 2012/09/13 10:45:04]

Removed "friend class TypeProfilerTest;" in the next patch.

+                           TestProfileNewWithoutProfiledDelete);
+
+  // It must be used only from allowed unit tests.  The following is only
+  // allowed for use in unit tests. Profiling should never be restarted in
+  // regular use.
+  static void Restart();
+};
+
+}  // namespace type_profiler
+}  // namespace base
+
+#endif  // BASE_ALLOCATOR_TYPE_PROFILER_CONTROL_H_