Have the Debugger extension api check that it has access to the tab

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

Index: chrome/browser/extensions/api/debugger/debugger_api_constants.cc
diff --git a/chrome/browser/extensions/api/debugger/debugger_api_constants.cc b/chrome/browser/extensions/api/debugger/debugger_api_constants.cc
index 70da45ba8805561040e6477f183600b5b134f76c..f20bcfce32063d8eab45a2404e1061a1c0b34a3d 100644
--- a/chrome/browser/extensions/api/debugger/debugger_api_constants.cc
+++ b/chrome/browser/extensions/api/debugger/debugger_api_constants.cc
@@ -10,6 +10,9 @@ const char kAlreadyAttachedError[] =
     "Another debugger is already attached to the * with id: *.";
 const char kAttachToWebUIError[] =
     "Can not attach to the page with the \"*://\" scheme.";
+const char kAttachToOtherExtensionError[] =
+    "Can not attach to another extension without the "
+    "'extensions-on-chrome-urls' command-line switch.";
 const char kNoTargetError[] = "No * with given id *.";
 const char kInvalidTargetError[] =
     "Either tab id or extension id must be specified.";