# Have Renderers wait: out / Default / bin / chrome_public_apk launch - args = "-renderer-wait-for-java-debugger" # Have tests wait: out / Default / bin / run_chrome_public_test_apk - wait - for - java - debugger out / Default / bin / run_chrome_junit_tests - wait - for - java - debugger # Specify custom port via -debug-socket=9999 Android Studio ExportedProperty ( category = "chrome" ) private int mSuperNiftyDrawingProperty Debugging Javaįor both apk and test targets, pass -wait-for-java-debugger to the wrapper scripts.Įxamples: # Install, launch, and wait: out / Default / bin / chrome_public_apk run - wait - for - java - debugger # Launch, and have GPU process wait rather than Browser process: out / Default / bin / chrome_public_apk launch - wait - for - java - debugger - debug - process - name privileged_process0 Want to add some additional information to your Views? You can do that by adding the annotation.Įxample. When building a local version of Chromium, the build tools automatically add android:debuggable=true to the AndroidManifest.xml, which will allow you to inspect them on rooted devices. Setting ANDROID_HVPROTO allows you to inspect debuggable apps on non-rooted devices. While your phone is plugged into USB, you can inspect the Android view hierarchy using the following command: ANDROID_HVPROTO = ddm monitor You can use either hierarchy viewer or monitor to see the Android view hierarchy and see the layout and drawing properties associated with it. envsetup.sh should have put it in your path. While your phone is plugged into USB, use the screenshot.py tool in build/android. Redirecting stdio to logcat, as documented here, has a bad side-effect that it breaks adb_install.py. # or: out / Default / bin / chrome_public_apk logcatĭo not use fprintf or printf debugging! This does not redirect to logcat. view chromium verbose logging, everything else at warning level with: adb logcat chromium : V cr. out / Default / bin / content_shell_apk launch 'data:text/html utf-8,Hello World!' out / Default / bin / chrome_public_apk launch 'data:text/html utf-8,Hello World!' Log outputĬhromium logging from LOG(INFO) etc., is directed to the Android logcat logging facility. You can launch the app by using one of the wrappers.
Get WebKit code to output to the adb log.Symbolizing Crash Stacks and Tombstones (C++).
0 kommentar(er)
