Add ability to retrieve a thread_name given a thread_id.

base/threading/thread.cc

Index: base/threading/thread.cc
diff --git a/base/threading/thread.cc b/base/threading/thread.cc
index 8e506ef4ec7347b4d0154717b2bac0ec21cedc00..9bc78b47ce08de6ef9c23668e4ddacf303f70a98 100644
--- a/base/threading/thread.cc
+++ b/base/threading/thread.cc
@@ -7,6 +7,7 @@
 #include "base/bind.h"
 #include "base/lazy_instance.h"
 #include "base/third_party/dynamic_annotations/dynamic_annotations.h"
+#include "base/threading/thread_id_name_manager.h"
 #include "base/threading/thread_local.h"
 #include "base/threading/thread_restrictions.h"
 #include "base/synchronization/waitable_event.h"
@@ -65,6 +66,7 @@ Thread::Thread(const char* name)
 
 Thread::~Thread() {
   Stop();
+  ThreadIdNameManager::GetInstance()->RemoveNameForId(thread_id_);

[jar (doing other things), 2013/01/24 01:05:14]

I would have expected that you'd leak this.  Is there anyone that would still
point to the interned (and I'd presumed, highly persistent) string?

[dsinclair, 2013/01/24 15:13:06]

The RemoveNameForId will remove the thread_id -> name mapping. The name still
exists in the name -> interned_name mapping which we'll lookup from next time we
want to use name. That item never gets free'd so it's essentially leaked.


On 2013/01/24 01:05:14, jar wrote:

 }
 
 bool Thread::Start() {