Remove redundant DevToolsManager methods and clean up its clients.

chrome/browser/extensions/api/debugger/debugger_api.cc

Index: chrome/browser/extensions/api/debugger/debugger_api.cc
diff --git a/chrome/browser/extensions/api/debugger/debugger_api.cc b/chrome/browser/extensions/api/debugger/debugger_api.cc
index 0af2f985022f70c46a6fe87158641aff2101903c..accb53203ae1fc740ce9893cb71da2d845f03563 100644
--- a/chrome/browser/extensions/api/debugger/debugger_api.cc
+++ b/chrome/browser/extensions/api/debugger/debugger_api.cc
@@ -525,10 +525,7 @@ bool DebuggerAttachFunction::RunImpl() {
 
   scoped_refptr<DevToolsAgentHost> agent(DevToolsAgentHost::GetOrCreateFor(
       contents_->GetRenderViewHost()));
-  DevToolsClientHost* client_host = DevToolsManager::GetInstance()->
-      GetDevToolsClientHostFor(agent);
-
-  if (client_host != NULL) {
+  if (DevToolsManager::GetInstance()->IsAttached(agent)) {

[pfeldman, 2013/03/29 14:59:23]

There already is IsDebuggerAttached(WebContents), consider aligning the two.

[Vladislav Kaznacheev, 2013/03/29 15:15:35]

There is, but it is not everywhere that we have WebContents (sometimes we only
have DTAH and it might point to a shared worker)
On 2013/03/29 14:59:23, pfeldman wrote:

     FormatErrorMessage(keys::kAlreadyAttachedError);
     return false;
   }