Add trace code to track all posted tasks in message_loop.

chrome/browser/sync/util/logging.h

Index: chrome/browser/sync/util/logging.h
diff --git a/chrome/browser/sync/util/logging.h b/chrome/browser/sync/util/logging.h
index b28efa2cf1790799c7d0819dca64f937b8c4f5b3..38b146617127d2e5027969b942de009cb770a2d1 100644
--- a/chrome/browser/sync/util/logging.h
+++ b/chrome/browser/sync/util/logging.h
@@ -22,7 +22,8 @@ bool VlogIsOnForLocation(const tracked_objects::Location& from_here,
 }  // 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)                              \