Try not to inline tcmalloc::Abort() so we can find it in stack trace.

third_party/tcmalloc/chromium/src/base/abort.cc

+// Copyright (c) 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.
+
+#include "base/abort.h"
+
+#if defined(TCMALLOC_USE_SYSTEM_ABORT)
+#include <stdlib.h>
+#endif
+#include "base/basictypes.h"
+
+namespace tcmalloc {
+
+// Don't inline so we can find Abort() call from stack trace.
+ATTRIBUTE_NOINLINE void Abort() {
+#if defined(TCMALLOC_USE_SYSTEM_ABORT)
+  abort();
+#else
+  // Make a segmentation fault to force abort.
+  *reinterpret_cast<volatile int*>(NULL) = 0x2001;

[jar (doing other things), 2012/06/08 21:02:31]

Suggest simplifying to never call system abort.

It might be useful to pick a specific address (not too far fro m void*(0) to be
modifying, rather than modifying NULL (which is sadly commonly referenced).

char* p = static_cast<char*>(NULL);
p += 57;  // Some interesting and searchable number.
*p = 0;

That might plausible help.... but searching for tcmalloc on crash stack will
probably get you the same results.

+#endif
+}
+
+} // namespace tcmalloc