Ensure that logging works in the GPU process when the --enable-logging and --v switches are specified.
This stopped working a long time back due to changes made to launch the GPU process under low integrity
mode on Vista+ which prevents write up operations on the files.
Fix is to add a sandbox policy allowing access to the log file and also pass the user-data-dir to the GPU
process. When the GPU process attempts to open the log file our intercepts kick in and broker the call
to the browser where the file is opened. I had to add an accessor to the logging code to return the log
file name.
Fixes bug https://code.google.com/p/chromium/issues/detail?id=178326
BUG=178326
R=jschuh, cpu
Review URL: https://chromiumcodereview.appspot.com/12319107
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@185055 0039d316-1c4b-4281-b951-d872f2087c98
diff --git a/base/logging.h b/base/logging.h
index 14e0426..79fa4a3 100644
--- a/base/logging.h
+++ b/base/logging.h
@@ -926,6 +926,11 @@
logging::RawLog(logging::LOG_FATAL, "Check failed: " #condition "\n"); \
} while (0)
+#if defined(OS_WIN)
+// Returns the default log file path.
+BASE_EXPORT std::wstring GetLogFileFullPath();
+#endif
+
} // namespace logging
// These functions are provided as a convenience for logging, which is where we
