Add trace code to track all posted tasks in message_loop.

chrome/browser/sync/util/logging.h

 // Copyright (c) 2011 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.
 
 #ifndef CHROME_BROWSER_SYNC_UTIL_LOGGING_H_
 #define CHROME_BROWSER_SYNC_UTIL_LOGGING_H_
 #pragma once
 
 #include "base/logging.h"
 
 // TODO(akalin): This probably belongs in base/ somewhere.
 
 namespace tracked_objects {
 class Location;
 }  // namespace tracked_objects
 
 namespace browser_sync {
 
 bool VlogIsOnForLocation(const tracked_objects::Location& from_here,
                          int verbose_level);
 
 }  // namespace browser_sync
 
 #define VLOG_LOC_STREAM(from_here, verbose_level)                       \
-  logging::LogMessage(from_here.file_name(), from_here.line_number(),   \
+  logging::LogMessage(from_here.file_name().as_string().c_str(),        \

[jar (doing other things), 2011/09/01 18:17:51]

I'm not clear on how often this logging is done... but this conversion to a
string and back may become a perf issue.

[jbates, 2011/09/01 23:01:52]

I agree if this is common we should add StringPiece support to LogMessage. Those
arguments aren't evaluated unless logging is enabled though, and when logging is
on, there are lots of string and stream operations that should make this
negligible.

+                      from_here.line_number(),                          \
                       -verbose_level).stream()
 
 #define VLOG_LOC(from_here, verbose_level)                              \
   LAZY_STREAM(                                                          \
       VLOG_LOC_STREAM(from_here, verbose_level),                        \
       VLOG_IS_ON(verbose_level) ||                                      \
       ::browser_sync::VlogIsOnForLocation(from_here, verbose_level))
 
 #endif  // CHROME_BROWSER_SYNC_UTIL_LOGGING_H_