android: Convert java_deobfuscate.py to Java

docs/android_debugging_instructions.md

 # Android Debugging Instructions
 
 Chrome on Android has java and c/c++ code. Each "side" have its own set of tools
 for debugging. Here's some tips.
 
 [TOC]
 
 ## Setting up command line flags
 
 Various commands below requires setting up command line flags.
@@ skipping 185 matching lines @@
 third_party/android_platform/development/scripts/stack --output-directory out/Default ~/crashlogs/tombstone_07-build231.txt
 ```
 
 ## Deobfuscating Stack Traces (Java)
 
 You will need the ProGuard mapping file that was generated when the application
 that crashed was built. When building locally, these are found in:
 
 ```shell
 out/Default/apks/ChromePublic.apk.mapping
-out/Default/apks/Chrome.apk.mapping
+out/Default/apks/ChromeModernPublic.apk.mapping
+etc.
 ```
 
-To deobfuscate a stack trace from a file, run
+Build the `java_deobfuscate` tool:
 
 ```shell
-build/android/stacktrace/java_deobfuscate.py PROGUARD_MAPPING_FILE.mapping --stacktrace STACKTRACE_FILE
+ninja -C out/Default java_deobfuscate
 ```
 
-Deobfuscation also works from `stdin`:
+Then run it via:
 
 ```shell
-adb logcat -d | build/android/stacktrace/java_deobfuscate.py PROGUARD_MAPPING_FILE.mapping
+# For a file:
+out/Default/bin/java_deobfuscate PROGUARD_MAPPING_FILE.mapping < FILE
+# For logcat:
+adb logcat | out/Default/bin/java_deobfuscate PROGUARD_MAPPING_FILE.mapping
 ```
 
 ## Get WebKit code to output to the adb log
 
 In your build environment:
 
 ```shell
 adb root
 adb shell stop
 adb shell setprop log.redirect-stdio true
@@ skipping 19 matching lines @@
 build/android/adb_gdb --output-directory=out/Default --package-name=org.chromium.native_test
 ```
 
 After attaching gdb to the process you can use it normally. For example:
 
 ```
 (gdb) break main
 Breakpoint 1 at 0x9750793c: main. (2 locations)
 (gdb) continue
 ```