diff options
| author | wangxianzhu@chromium.org <wangxianzhu@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-11-01 21:38:14 +0000 |
|---|---|---|
| committer | wangxianzhu@chromium.org <wangxianzhu@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-11-01 21:38:14 +0000 |
| commit | f9dba0ca2735321a4a6bd6c6d1cc977e7e554a3e (patch) | |
| tree | b24ff0381fdc047acd0afcee60896deac9365490 /base/base.gypi | |
| parent | 6891c0d244613a6c5f0606d61ec2868348a45533 (diff) | |
| download | chromium_src-f9dba0ca2735321a4a6bd6c6d1cc977e7e554a3e.zip chromium_src-f9dba0ca2735321a4a6bd6c6d1cc977e7e554a3e.tar.gz chromium_src-f9dba0ca2735321a4a6bd6c6d1cc977e7e554a3e.tar.bz2 | |
Make Chrome Trace work with Android ATrace.
It uses "view" tag in the ATrace to enable tracing Chrome events.
Steps to grab a trace:
1. Enable trace of "view" in the Developer options.
2. adb shell stop; adb shell start
or if the system itself supports changing trace settings without restart:
adb shell am force-stop com.android.chrome (for stable version)
adb shell am force-stop com.google.android.apps.chrome (for beta/dev version)
3. Start Chrome
4. // grab a 5-seconds trace, the result is in trace.html
third_party/android_tools/sdk/tools/systrace/systrace.py -t 5 -f -w
Note: the intent triggered Chrome trace still works with this patch.
BUG=
Review URL: https://chromiumcodereview.appspot.com/11345019
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@165507 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'base/base.gypi')
| -rw-r--r-- | base/base.gypi | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/base/base.gypi b/base/base.gypi index 905dd4c..b8b5fa0 100644 --- a/base/base.gypi +++ b/base/base.gypi @@ -114,6 +114,7 @@ 'debug/stack_trace_win.cc', 'debug/trace_event.cc', 'debug/trace_event.h', + 'debug/trace_event_android.cc', 'debug/trace_event_impl.cc', 'debug/trace_event_impl.h', 'debug/trace_event_win.cc', |