# Debugging native code with ndk-gdb using standalone CMake toolchain

I recently ran into this problem and could not find any good solution on the Internet. So next comes a small summary of the problem with hopefully enough buzzwords, so Google can lead you here.

If you want to do C++ development on Android, you need the NDK for cross compilation. It comes by default with its own build system called ndk-build, which basically is a bunch of custom makefiles. But if you are sharing code between the Android Platform and lets say plain Linux, you have likely already a build system installed. For C/C++ CMake is quite popular as it supports different platforms and compilers. Fortunately there is already a project which adds Android support to CMake. I will not cover that – instead I assume you are using it already.

Unfortunately you cant use the ndk-gdb script supplied with the NDK to debug your application as it relies on the behaviour of ndk-build. But as said earlier, ndk-build is no wizardy, but just a bunch of scripts. So it is possible to emulate the behaviour using CMake, as following:

macro(ndk_gdb_debuggable TARGET_NAME)
get_property(TARGET_LOCATION TARGET ${TARGET_NAME} PROPERTY LOCATION) # create custom target that depends on the real target so it gets executed afterwards add_custom_target(NDK_GDB ALL) add_dependencies(NDK_GDB${TARGET_NAME})

set(GDB_SOLIB_PATH ${PROJECT_SOURCE_DIR}/obj/local/${ANDROID_NDK_ABI_NAME}/)

# 1. generate essential Android Makefiles
file(WRITE ${PROJECT_SOURCE_DIR}/jni/Android.mk "APP_ABI :=${ANDROID_NDK_ABI_NAME}\n")
file(WRITE ${PROJECT_SOURCE_DIR}/jni/Application.mk "APP_ABI :=${ANDROID_NDK_ABI_NAME}\n")

# 2. generate gdb.setup
get_directory_property(PROJECT_INCLUDES DIRECTORY ${PROJECT_SOURCE_DIR} INCLUDE_DIRECTORIES) string(REGEX REPLACE ";" " " PROJECT_INCLUDES "${PROJECT_INCLUDES}")
file(WRITE ${PROJECT_SOURCE_DIR}/libs/${ANDROID_NDK_ABI_NAME}/gdb.setup "set solib-search-path ${GDB_SOLIB_PATH}\n") file(APPEND${PROJECT_SOURCE_DIR}/libs/${ANDROID_NDK_ABI_NAME}/gdb.setup "directory${PROJECT_INCLUDES}\n")

# 3. copy gdbserver executable
file(COPY ${ANDROID_NDK}/prebuilt/android-arm/gdbserver/gdbserver DESTINATION${PROJECT_SOURCE_DIR}/libs/${ANDROID_NDK_ABI_NAME}/) # 4. copy lib to obj add_custom_command(TARGET NDK_GDB POST_BUILD COMMAND mkdir -p${GDB_SOLIB_PATH})
add_custom_command(TARGET NDK_GDB POST_BUILD COMMAND cp ${TARGET_LOCATION}${GDB_SOLIB_PATH})

# 5. strip symbols
add_custom_command(TARGET NDK_GDB POST_BUILD COMMAND ${CMAKE_STRIP}${TARGET_LOCATION})
endmacro()

Then use it like

add_library(YourTarget ...)
ndk_gdb_debuggable(YourTarget)


You should now be able to use ndk-gdb with CMake, just as if you would have used ndk-build.

Note that steps 4 and 5 are optional for debugging. They just reduce the size of the library that has to be transferred to the device. If you dont care, you can just leave them out. But then the solib search path from step 2 must be set to:

file(WRITE ./libs/${ANDROID_NDK_ABI_NAME}/gdb.setup "set solib-search-path ./libs/${ANDROID_NDK_ABI_NAME}\n")

Ideally someone should integrate that in the Android toolchain linked above.

Update Merged Upstream

• iwasz

Thanks for this info. It was very helpful for me. Thumbs up!

• Dave

Thanks heaps for this. Was just looking for the strip command, but the rest would be awesome as well

• Sean

GREAT! Used both the GDB and the strip, Works like charm, priceless. Thank you very much!