Our experience has been that ndk-debug is completely useless for debugging something like pjsua on Android. We found it to be a complete waste of time. We are working with the Linaro stuff to build an Android development system that has native gdb, because we need the ability to debug things like pjsua on Android ourselves. And no, we don't have native gdb working yet. Craig Vanderborgh Voxware Incorporated On Fri, Aug 17, 2012 at 2:17 PM, Shaun Clark <shaun_clark at hotmail.com> wrote: > Is there a way to debug this using the ndk debugger in Android? I tried this > series of calls to detect the new ip address after switching between wifi > and 3g: > > pj_str_t new_contact; > > new_contact = pjsua_var.acc[2].contact; > > __android_log_print(ANDROID_LOG_DEBUG, "main_android", "current contact %s", > new_contact); > > > pjsua_detect_nat_type(); > > > after switch the "pjsua_detect_nat_type()" causes a fatal signal 11, which I > have come to find just means crashing. When I try to run ndk-gdb from the > project directory per the directions: > > > /pjsip-android/pjsip-apps/src/apjsua, I get: > > ndk-gdb > > /android-ndk-r8//build/core/add-application.mk:133: *** Android NDK: > Aborting... . Stop. > > ERROR: The device does not support the application's targetted CPU ABIs! > > Device supports: armeabi-v7a armeabi > > Package supports: Android NDK: Your APP_BUILD_SCRIPT points to an > unknown file: ./jni/Android.mk > > > any help on either issue would be great, thanks! > > > Shaun > > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > -- "Without forgiveness one remains a prisoner of one's past" -- John Paul II
