Change Chromoting logger to be setup in plugin's NP_Initialize.

remoting/client/plugin/chromoting_scriptable_object.cc

Index: remoting/client/plugin/chromoting_scriptable_object.cc
diff --git a/remoting/client/plugin/chromoting_scriptable_object.cc b/remoting/client/plugin/chromoting_scriptable_object.cc
index 28c630397145cd0433c2adfeedb56044397ae988..86bfc498780fcbe6a7f8134d119f0638cdb48ebe 100644
--- a/remoting/client/plugin/chromoting_scriptable_object.cc
+++ b/remoting/client/plugin/chromoting_scriptable_object.cc
@@ -253,8 +253,10 @@ void ChromotingScriptableObject::LogDebugInfo(const std::string& info) {
   cb.Call(Var(), Var(info), &exception);
 
   if (!exception.is_undefined()) {
-    LOG(WARNING) << "Exception when invoking debugInfo JS callback: "
-                 << exception.DebugString();
+    // Note that we cannot use LOG here because we're currently in the middle
+    // of handling a LOG message.

[Wez, 2011/08/30 05:20:02]

We've got a check that prevents recursive calling in to this function, so we can
LOG() here and it'll just go to the other log handlers, surely?

[garykac, 2011/08/31 00:59:00]

The previous checks didn't work because they were only protecting the post, not
the actual code that handled the log message.

The checks that are there need to be removed.

I'm creating a 2nd cl for client log cleanup and moving these changes into that
cl.

+    printf("Exception when invoking debugInfo JS callback: %s\n",
+           exception.DebugString());
   }
 }