android_debugging

[vinjn]

C:\Downloads\adt-bundle-windows-x86-20130219\sdk\tools\monitor.bat

Register	APCS name	APCS Role
R0-R3	a1-a4	argument 1-4/scratch register/result
R4-R8	v1-v5	register variable
R9	sb/v6	static base/register variable
R10	sl/v7	stack limit/stack chunk handle/register variable
R11	fp/v8	frame pointer/register variable
R12	ip	scratch register/new-sb in inter-link-unit calls
R13	sp	lower end of the current stack frame
R14	lr	link register/scratch register
R15	pc	program counter
R16	cpsr	ARM processor mode indicator
D0-DN		Double precision registers (N)

[vinjn]

Android architecture consists of the following layers:

• Applications layer - set of core applications including an email client, SMS program, calendar, maps, browser etc. All applications are written using the Java programming language.
• Application Framework – set of standard components and user services (written using the Java) which help to implement the standard structure of an application.
• Libraries - a set of C/C++ libraries used by various components of the Android system.
• Android runtime - a set of core libraries that provides most of the functionality available in the core libraries of the Java programming language.
• Linux Kernel - core system services such as security, memory management, process management, network stack, and driver model. The kernel also acts as an abstraction layer between the hardware and the rest of the software stack.

[vinjn]

http://www.kandroid.org/online-pdk/guide/debugging_gdb.html

[vinjn]

To direct printf to logcat

echo "log.redirect-stdio = true" > /data/local.prop

[vinjn]

adb shell cat /data/tombstones/tombstone_00 | ndk-stack -sym solution/obj/local/armeabi/

print human-readable callstack

[vinjn]

You don't need to use -O0 or -g switches. You need to do one of following:

• put android:debuggable="true" to the tag in AndroidManifest.xml file
• use NDK_DEBUG=1 after ndk-build
• put APP_OPTIM := debug in Application.mk file
• Doing anyone of these three things will automatically use -O0 and -g switches.

Can you try running gdb manually, without gdb script? It involves following steps:

• pushing gdbserver file to /data/local folder on device
• running your application & invoking in adb shell following command gdbserver :5055 --attach PID, where PID is your application process id.
• running adb forward tcp:5055 tcp:5055 on host
• running arm-linux-androideabi-gdb.exe from your app folder entering following commands in gdb

set solib-search-path obj/local/armeabi
file obj/local/armeabi/libMySharedLib.so
target remote :5055

And see if you can debug then.

If you want see symbols for other shared libraries your library is using like libc.so, then pull them from device (from /system/lib folder) to your obj/local/armeabi folder.

[vinjn]

ndk-gdb --start com.nvidia.trex.TREXActivity --force --verbose

[vinjn]

http://software.intel.com/en-us/articles/how-to-test-and-debug-ndk-based-android-applications

[vinjn]

adb driver http://visualgdb.com/UsbDriverTool/UsbDriverTool-sfx.exe