summaryrefslogtreecommitdiff
path: root/README.Android
diff options
context:
space:
mode:
authorMiklos Vajna <vmiklos@collabora.co.uk>2014-12-08 16:25:49 +0100
committerMiklos Vajna <vmiklos@collabora.co.uk>2014-12-08 16:27:32 +0100
commit1256809ba235e1813b38bb7e96d8f1a6c5b6499f (patch)
tree0a64a52571e4e83bfab5b41247ec109a570b9a86 /README.Android
parent8ab56d59735048836f0b121e45638b3c5ad1b252 (diff)
README.Android: mention ndk-gdb --start
Change-Id: Ib131c480b53665fc9e9a38388e3cc179eac249c2
Diffstat (limited to 'README.Android')
-rw-r--r--README.Android23
1 files changed, 5 insertions, 18 deletions
diff --git a/README.Android b/README.Android
index 9ae7fd3ec04f..98a109d8d07e 100644
--- a/README.Android
+++ b/README.Android
@@ -46,27 +46,14 @@ know. But don't seem to be necessary on a real device anyway?
* Debugging
- Install the .apk to the device, start the application, and:
+ Install the .apk to the device, and:
cd android/experimental/LOAndroid3
- <android-ndk-r9d>/ndk-gdb --adb=<android-sdk-linux>/platform-tools/adb
+ <android-ndk-r10d>/ndk-gdb --adb=<android-sdk-linux>/platform-tools/adb --start
- Some versions of the NDK had a broken gdb in the way that it can see
-symbols only for shlibs that were already loaded when the debuggee was
-attached, so you need to carefully guess where to put:
-
- fprintf(stderr, "Sleeping NOW!\n"); ::sleep(20);
-
- into the code; and when you see that in logcat, you have time
-to run: ndk-gdb and it will attach the process.
-
- thread 12 # or perhaps 13
- backtrace
-
- may show you the native code trace.
-
- In r8b the ndk-gdb seems to work a bit better, and I think it isn't
-necessary to use the mingw-and-ndk ndb-gdb any longer.
+ It seems that the "have to start the app before gdb can connect to it"
+and the "pending breakpoints do not work" problems are now resolved with the
+current NDK.
* Getting the symbols