chromium/src
0
Fork 0
Code Activity

Turn on standard logging details in Mojo app runners

Browse Source 
It's not clear why Mojo runner disabled these, and I think
the mash runner just copied whatever the Mojo runner was doing.

BUG=None

Review URL: https://codereview.chromium.org/1835653002

Cr-Commit-Position: refs/heads/master@{#383373}
This commit is contained in:
rockot
2016-03-25 14:48:18 -07:00
committed by Commit bot
parent e3cc7bce01
commit 317d7f244d
2 changed files with 8 additions and 8 deletions
chrome/app/mash
mash_runner.cc
mojo/shell/runner
init.cc

8
chrome/app/mash/mash_runner.cc

@ -219,10 +219,10 @@ int MashMain() {
settings.logging_dest = logging::LOG_TO_SYSTEM_DEBUG_LOG;
logging::InitLogging(settings);
// To view log output with IDs and timestamps use "adb logcat -v threadtime".
logging::SetLogItems(false, // Process ID
false, // Thread ID
false, // Timestamp
false); // Tick count
logging::SetLogItems(true, // Process ID
true, // Thread ID
true, // Timestamp
true); // Tick count
// TODO(sky): use MessagePumpMojo.
scoped_ptr<base::MessageLoop> message_loop;

8
mojo/shell/runner/init.cc

@ -32,10 +32,10 @@ void InitializeLogging() {
settings.logging_dest = logging::LOG_TO_SYSTEM_DEBUG_LOG;
logging::InitLogging(settings);
// To view log output with IDs and timestamps use "adb logcat -v threadtime".
logging::SetLogItems(false, // Process ID
false, // Thread ID
false, // Timestamp
false); // Tick count
logging::SetLogItems(true, // Process ID
true, // Thread ID
true, // Timestamp
true); // Tick count
}
void WaitForDebuggerIfNecessary() {