android - NDK debugging: ndk-gdb fails to pull app_process. Who and when creates the app_process binary? -

android - NDK debugging: ndk-gdb fails to pull app_process. Who and when creates the app_process binary? -

while investigating problem hitting breakpoints in native code, decided check if ndk-gdb works ok. i've deleted app_process, started java debugging , ran ndk-gdb --force. guess what, app_process not created. ndk-gdb --verbose output has line :

## command: adb_cmd pull /system/bin/app_process obj/local/armeabi-v7a/app_process remote object '/system/bin/app_process' not file or directory pulled app_process device/emulator.

i've uninstalled app target device, rebooted device , repeated. still no app_process. so, wonder what's problem here, , wonder when file created, , process / script.

as mentioned before, android 5.0 has /system/bin/app_process symlink /system/bin/app_process32. since symlink cannot pulled adb pull, ndk-gdb script not able work as-is.

change ndk-gdb follows back upwards api21 changes backwards compatibility < api21:

# app_server binary device app_process=$app_out/app_process if [ "$api_level" -lt "21" ] ; run adb_cmd pull /system/bin/app_process `native_path $app_process` log "pulled app_process device/emulator $app_process" else run adb_cmd pull /system/bin/app_process32 `native_path $app_process` log "pulled app_process32 device/emulator $app_process" fi

edit: or:

# app_server binary device app_process=$app_out/app_process app_process_device=app_process32 if [ "$api_level" -lt "21" ] ; app_process_device=app_process fi run adb_cmd pull /system/bin/$app_process_device `native_path $app_process` log "pulled $app_process_device device/emulator $app_process"

original alter here: http://pastebin.com/yfxns06u. note alter renames app_process32 app_process when pulled development machine back upwards having single debugging config in eclipse.

android windows debugging android-ndk eclipse-adt