chromium/src
0
Fork 0
Code Activity

android_debugging_instructions.md: Add fix for "Attach to Local Process"

Browse Source 
Change-Id: Ib9fae5803392c2af7f5951b6645f2b9dc07e9506
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3715369
Reviewed-by: Peter Wen <wnwen@chromium.org>
Auto-Submit: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Peter Wen <wnwen@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1015971}
This commit is contained in:
Andrew Grieve
2022-06-20 18:48:45 +00:00
committed by Chromium LUCI CQ
parent 5b510e1c0e
commit f189506013
1 changed files with 1 additions and 0 deletions

1
docs/android_debugging_instructions.md

@ -77,6 +77,7 @@ out/Default/bin/run_chrome_junit_tests --wait-for-java-debugger # Specify custo
* Click "Run"->"Attach debugger to Android process" (see
[here](https://developer.android.com/studio/debug/index.html) for more).
* Click "Run"->"Attach to Local Process..." for Robolectric junit tests.
* If this fails, you likely need to follow [these instructions](https://stackoverflow.com/questions/21114066/attach-intellij-idea-debugger-to-a-running-java-process).
### Eclipse
* In Eclipse, make a debug configuration of type "Remote Java Application".