From 574036712fa0d0347e088333117ed2ef99c087f5 Mon Sep 17 00:00:00 2001 From: "sgjesse@chromium.org" Date: Thu, 6 Nov 2008 10:39:35 +0000 Subject: Changed the call to attach the debugger to V8 to run in the renderer thread. With V8 r648 (Review URL: http://codereview.chromium.org/8909) attaching the debugger to V8 will initialize V8 if not already initialized. This needs to be serialized with the initialization of V8 in the renderer thread. This change does not require the changes in V8 r648, but will not have any effect without. Added a few comments. BUG=3723 Review URL: http://codereview.chromium.org/8735 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@4875 0039d316-1c4b-4281-b951-d872f2087c98 --- chrome/renderer/debug_message_handler.h | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'chrome/renderer/debug_message_handler.h') diff --git a/chrome/renderer/debug_message_handler.h b/chrome/renderer/debug_message_handler.h index f02ad88..9720ef1 100644 --- a/chrome/renderer/debug_message_handler.h +++ b/chrome/renderer/debug_message_handler.h @@ -21,9 +21,12 @@ class DebugMessageHandler : public IPC::ChannelProxy::MessageFilter, virtual ~DebugMessageHandler(); private: - // evaluate javascript URL in the renderer + // Evaluate javascript URL in the renderer void EvaluateScript(const std::wstring& script); + // Attach in the renderer + void Attach(); + // Debugger::Delegate callback method to handle debugger output. void DebuggerOutput(const std::wstring& out); -- cgit v1.1