| commit | e2b55cc55202bd9e34e991931deaeb059fb01f23 | [log] [tgz] |
|---|---|---|
| author | Stefan Zager <[email protected]> | Fri Oct 04 19:57:54 2019 |
| committer | Commit Bot <[email protected]> | Fri Oct 04 19:57:54 2019 |
| tree | cd009e789c703b57661e698792ad639238e71790 | |
| parent | ffee101a23f5fef9152b8bdcb03a84ea5cc1b007 [diff] [blame] |
Documentation: remove ASAN setup prior to running gdb on android [email protected] Change-Id: I958743633dfca88c9f7b20aa1af2bd34719970bd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1841577 Auto-Submit: Stefan Zager <[email protected]> Reviewed-by: Andrew Grieve <[email protected]> Commit-Queue: Andrew Grieve <[email protected]> Cr-Commit-Position: refs/heads/master@{#703005}
diff --git a/docs/android_debugging_instructions.md b/docs/android_debugging_instructions.md index d9df558..92d964e 100644 --- a/docs/android_debugging_instructions.md +++ b/docs/android_debugging_instructions.md
@@ -116,6 +116,17 @@ Failed to read a valid object file image from memory. ``` +If you have ever run an ASAN build of chromium on the device, you may get +an error like the following when you start up gdb: +``` +/tmp/<username>-adb-gdb-tmp-<pid>/gdb.init:11: Error in sourced command file: +"/tmp/<username>-adb-gdb-tmp-<pid>/app_process32": not in executable format: file format not recognized +``` +If this happens, run the following command and try again: +```shell +$ src/android/asan/third_party/asan_device_setup.sh --revert +``` + ### Using Visual Studio Code While the app is running, run the `gdb` command with `--ide`: