chromium/src
0
Fork 0
Code Activity

Documentation: remove ASAN setup prior to running gdb on android

Browse Source 
R=agrieve@chromium.org

Change-Id: I958743633dfca88c9f7b20aa1af2bd34719970bd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1841577
Auto-Submit: Stefan Zager <szager@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Andrew Grieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703005}
This commit is contained in:
Stefan Zager
2019-10-04 19:57:54 +00:00
committed by Commit Bot
parent ffee101a23
commit e2b55cc552
1 changed files with 11 additions and 0 deletions

11
docs/android_debugging_instructions.md

@ -116,6 +116,17 @@ Do you need "set solib-search-path" or "set sysroot"?
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`: