aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorJose Luis Marti <joseluis.marti@gmail.com>2022-11-06 23:00:15 +0100
committerJose Luis Marti <joseluis.marti@gmail.com>2022-11-06 23:00:15 +0100
commitc61b4fcabc9ec9388d839765f10a42e309c754ab (patch)
treedfb2636a8b5197a71a7b43d4616a922e4b55f3e4 /docs
parent4bc047f5ad039432ab5030111032fc050889303a (diff)
Update how to start ndk-gdb
Diffstat (limited to 'docs')
-rw-r--r--docs/README.Android.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/README.Android.md b/docs/README.Android.md
index cb9cd9b381..cd9fac0c09 100644
--- a/docs/README.Android.md
+++ b/docs/README.Android.md
@@ -368,11 +368,11 @@ Enable CheckJNI (**before** starting the Kodi):
adb shell setprop debug.checkjni 1
```
-**NOTE:** These commands assume that current directory is `tools/android/packaging` and that the proper SDK/NDK paths are set.
+**NOTE:** These commands assume that current directory is `$HOME/kodi-build/tools/android/packaging` and that the proper SDK/NDK paths are set.
-GDB can be used to debug, though the support is rather primitive. Rather than using gdb directly, you will need to use ndk-gdb which wraps it. Do **not** trust the `-p/--project` switches, as they do not work. Instead you will need to `cd` to `tools/android/packaging/xbmc` and execute it from there.
+GDB can be used to debug, though the support is rather primitive. Rather than using `gdb` directly, you will need to use `ndk-gdb` which wraps it. You can use the `-p/--project` switches or instead you will need to `cd` to `$HOME/kodi-build/tools/android/packaging/xbmc` and execute it from there.
```
- ndk-gdb --start --delay=0
+ ndk-gdb --verbose
```
This will open the installed version of Kodi and break. The warnings can be ignored as we have the appropriate paths already setup.