Fix the android symbolization instructions.

docs/android_test_instructions.md

Index: docs/android_test_instructions.md
diff --git a/docs/android_test_instructions.md b/docs/android_test_instructions.md
index 008c7cca34acc05870364fba128c9cfb11cd830f..988bb7ae92c216bbbf0a845f60875980808b6903 100644
--- a/docs/android_test_instructions.md
+++ b/docs/android_test_instructions.md
@@ -152,8 +152,8 @@ tune2fs -e continue android_emulator_sdk/sdk/system-images/android-23/x86/userda
 Crash stacks are logged and can be viewed using adb logcat. To symbolize the
 traces, pipe the output through
 `third_party/android_platform/development/scripts/stack`. If you build in an
-output directory other than "out", pass
-`--chrome-symbols-dir=out_directory/{Debug,Release}/lib` to the script as well.
+output directory other than "out/{Debug,Release}", pass
+`--chrome-symbols-dir=out_path` to the script as well.

[agrieve, 2015/12/18 20:19:33]

I think you should give explicit examples for both GYP and GN, since with
--chrome-symbols-dir, you need to pass it out/Debug/lib on GYP and
out/Debug/lib.unstripped for GN.

Alternatively, it's might be better to do promote the use of:
CHROMIUM_OUTPUT_DIR=path/to/out/Debug
third_party/android_platform/development/scripts/stack

since then the script will look for both lib and lib.unstripped within there.

[Jeffrey Yasskin, 2015/12/18 21:00:06]

How's this?

 
 ## JUnit tests