Fix backwards WebRTC-in-Chromium override and expose Chromium logging setup

third_party/webrtc_overrides/webrtc/base/logging.h

 // Copyright 2015 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 // This file overrides the logging macros in WebRTC (webrtc/base/logging.h).
 // Instead of using WebRTC's logging implementation, the WebRTC macros are
 // mapped to DIAGNOSTIC_LOGING. In it's implementation (DiagnosticLogMessage in
 // third_party/webrtc_overrides/webrtc/base/logging.h), the corresponding
 // base/logging.h macros (e.g. Chromium's VLOG) are used.
 // If this file is included outside of WebRTC/libjingle it should be included
 // after base/logging.h (if any) or compiler error or unexpected behavior may
 // occur (macros that have the same name in WebRTC as in Chromium will use
 // the WebRTC definition if this file is included first).
 
 // Setting the LoggingSeverity (and lower) that should be written to file should
 // be done via command line by specifying the flags:
 // --vmodule or --v please see base/logging.h for details on how to use them.
 // Specifying what file to write to is done using InitLogging also in
 // base/logging.h.
 
 // The macros and classes declared in here are not described as they are
 // NOT TO BE USED outside of WebRTC/libjingle.
 
 #ifndef THIRD_PARTY_WEBRTC_OVERRIDES_WEBRTC_BASE_LOGGING_H_
 #define THIRD_PARTY_WEBRTC_OVERRIDES_WEBRTC_BASE_LOGGING_H_
 
 #include "third_party/webrtc_overrides/webrtc/base/diagnostic_logging.h"
 
+// Chromium allows a minimum programmatically-set log level of -1

[Henrik Grunell, 2016/05/18 08:43:26]

Explain that this function is only used when WebRTC standalone is built but it
used the Chromium logging.

Add TODO for removing it when the fuzzers are built/run on WebRTC bots, i.e. not
inside Chromium. (Sorry for any incorrect/confused terminology...:)) Link to
bug.

[katrielc, 2016/05/18 09:06:42]

I checked with phoglund@ and they don't plan to move the ClusterFuzz uploads to
the WebRTC bot, hence probably it makes sense not to add a TODO/bug link.

[Henrik Grunell, 2016/05/18 09:29:32]

Acknowledged.

+// unless there is a command line set up with --v=x. This exposes
+// those initialisation calls to WebRTC code.
+namespace rtc {
+  void InitChromiumLoggingAndCommandLine();
+}
+
 //////////////////////////////////////////////////////////////////////
 // WebRTC macros which in DiagnosticLogMessage are mapped over to
 // their VLOG equivalent in base/logging.h.
 //////////////////////////////////////////////////////////////////////
 
 #if defined(LOGGING_INSIDE_WEBRTC)
 
 #include <errno.h>
 
 namespace rtc {
@@ skipping 47 matching lines @@
 #define LOG_ERR(sev) LOG_ERRNO(sev)
 #define LAST_SYSTEM_ERROR (errno)
 #endif  // OS_WIN
 
 #undef PLOG
 #define PLOG(sev, err) LOG_ERR_EX(sev, err)
 
 #endif  // LOGGING_INSIDE_WEBRTC
 
 #endif  // THIRD_PARTY_WEBRTC_OVERRIDES_WEBRTC_BASE_LOGGING_H_