DevTools: Nuke legacy debugger.

Review URL: http://codereview.chromium.org/146027

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

1 files changed, 0 insertions, 18 deletions

diff --git a/chrome/browser/debugger/debugger_wrapper.h b/chrome/browser/debugger/debugger_wrapper.h
index 943b816..1a29566 100644
--- a/chrome/browser/debugger/debugger_wrapper.h
+++ b/chrome/browser/debugger/debugger_wrapper.h
@@ -5,15 +5,6 @@
 // Include this file if you need to access the Debugger outside of the debugger
 // project.  Don't include debugger.h directly.  If there's functionality from
 // Debugger needed, add new wrapper methods to this file.
-//
-// This is a workaround to enable the Debugger without breaking the KJS build.
-// It wraps all methods in Debugger which are called from outside of the
-// debugger project.  Each solution has its own project with debugger files.
-// KJS has only debugger_wrapper* and debugger.h, and defines
-// CHROME_DEBUGGER_DISABLED, which makes it compile only a stub version of
-// Debugger that doesn't reference V8.  Meanwhile the V8 solution includes all
-// of the debugger files without CHROME_DEBUGGER_DISABLED so the full
-// functionality is enabled.
 
 #ifndef CHROME_BROWSER_DEBUGGER_DEBUGGER_WRAPPER_H_
 #define CHROME_BROWSER_DEBUGGER_DEBUGGER_WRAPPER_H_
@@ -33,16 +24,7 @@ class DebuggerWrapper : public base::RefCountedThreadSafe<DebuggerWrapper> {
 
   virtual ~DebuggerWrapper();
 
-  void SetDebugger(DebuggerHost* debugger);
-  DebuggerHost* GetDebugger();
-
-  void DebugMessage(const std::wstring& msg);
-
-  void OnDebugAttach();
-  void OnDebugDisconnect();
-
  private:
-  scoped_refptr<DebuggerHost> debugger_;
   scoped_refptr<DevToolsProtocolHandler> proto_handler_;
 };