commit | e0021d397103bc9bfa4f246cdfcebd8c8ccd77d3 | [log] [tgz] |
---|---|---|
author | David Van Cleve <[email protected]> | Wed Jan 29 16:02:58 2020 |
committer | Commit Bot <[email protected]> | Wed Jan 29 16:02:58 2020 |
tree | 6f0408236ffad3b7e3861c8c406eb1ae2353dfb1 | |
parent | 90cddf00fafc2e1806c40d3d9ee2e124e24f3ee3 [diff] [blame] |
Update Android debugging docs to suggest `adb logcat`. I wasn't able to see my LOG(INFO) output when running the test binary with `logcat -v` added, but a colleague suggested `adb logcat`, which worked. This CL updates the Android debugging docs to suggest `adb logcat` for viewing printed log lines. Change-Id: Iec2152b9fb5ca265239e7515482ff7be823eddca Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2023390 Commit-Queue: David Van Cleve <[email protected]> Reviewed-by: Peter Wen <[email protected]> Cr-Commit-Position: refs/heads/master@{#736386}
diff --git a/docs/android_debugging_instructions.md b/docs/android_debugging_instructions.md index 92d964e..5b1983d8 100644 --- a/docs/android_debugging_instructions.md +++ b/docs/android_debugging_instructions.md
@@ -25,6 +25,9 @@ out/Default/bin/chrome_public_apk logcat [-v] # Use -v to show logs for other processes ``` +If this doesn't display the logs you're looking for, try `adb logcat` with your system `adb` +or the one in `//third_party/android_sdk/`. + ### Warnings for Blink developers * **Do not use fprintf or printf debugging!** This does not redirect to logcat.