Added unique function names (IOThreadRun, DBThreadRun, etc)

which make it possible to tell the thread name in crash dumps
from the call stack. Added a volatile automatic variable to
avoid global optimizers optimizing the function.

This change would help us to triage ThreadWatcher crashes
for IO thread. It would also help in debugging crashes.

R=sky, jar
Review URL: https://chromiumcodereview.appspot.com/10796079

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@147949 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 12 insertions, 0 deletions

diff --git a/content/browser/browser_thread_impl.h b/content/browser/browser_thread_impl.h
index eb883ed..9eaeb68 100644
--- a/content/browser/browser_thread_impl.h
+++ b/content/browser/browser_thread_impl.h
@@ -27,6 +27,7 @@ class CONTENT_EXPORT BrowserThreadImpl
 
  protected:
   virtual void Init() OVERRIDE;
+  virtual void Run(MessageLoop* message_loop) OVERRIDE;
   virtual void CleanUp() OVERRIDE;
 
  private:
@@ -35,6 +36,17 @@ class CONTENT_EXPORT BrowserThreadImpl
   // the API cleaner. Therefore make BrowserThread a friend class.
   friend class BrowserThread;
 
+  // The following are unique function names that makes it possible to tell
+  // the thread id from the callstack alone in crash dumps.
+  void UIThreadRun(MessageLoop* message_loop);
+  void DBThreadRun(MessageLoop* message_loop);
+  void WebKitThreadRun(MessageLoop* message_loop);
+  void FileThreadRun(MessageLoop* message_loop);
+  void FileUserBlockingThreadRun(MessageLoop* message_loop);
+  void ProcessLauncherThreadRun(MessageLoop* message_loop);
+  void CacheThreadRun(MessageLoop* message_loop);
+  void IOThreadRun(MessageLoop* message_loop);
+
   static bool PostTaskHelper(
       BrowserThread::ID identifier,
       const tracked_objects::Location& from_here,