摘要:Android手机操作系统中的dalvik虚拟机起到了执行应用程序的作用,为整个android平台中的核心组件之一。本文介绍了在x86架构上对dalvik虚拟机进行配置并使用GDB对dalvik进行调试的方法。
关键字:Android,Dalvik VM,X86,GDB
Target 1: Setup Eclipse for dalvik source code
(Using tree to make folder ordered). Open Eclipse, choose new project, name it. Import dalvik dictionary inside android root path. Click finish. Do not include unnecessary files in your project, like files in .git dictionary.
Target 2: Build dalvik for x86 architecture
In the latest version of Android 2.3.4, system already build a x86 dalvik in /android-root/out/host/linux-x86/bin/
Target 3: GDB dalvik
Running dalvikvm in x86 need some preparation:
1, Set up Android_Root. The Android_Root is set to host dictionary, ANDROID_ROOT=/home/user/android_src_2.3.4/out/host/linux-x86/. (Not target dictionary because we actually running dalvik in x86 platform)
2, Set ANDROID_DATA.
export ANDROID_DATA=/tmp/dalvik_$USER
mkdir -p $ANDROID_DATA/dalvik-cache
This is totally unnecessary but however android choose to do this.
3, Set pre-load Java libraries
export DALVIK_VM_INIT_CLASS_PATH=/home/lijian/android_src_2.3.4/out/target/product/generic/system/framework/core.jar:/home/lijian/android_src_2.3.4/out/target/product/generic/system/framework/android.policy.jar:/home/lijian/android_src_2.3.4/out/target/product/generic/system/framework/services.jar:/home/lijian/android_src_2.3.4/out/target/product/generic/system/framework/framework.jar:/home/lijian/android_src_2.3.4/out/target/product/generic/system/framework/ext.jar
(Note: The *.jar file are all in target dictionary because all Java files in host dictionary are NOT compiled into dex form. This is strange to debug dalvik in x86 platform but will be more simple if you debug in Arm directly).
And then use Javac and dx compile a HelloWorld
Run dalvik:
./out/host/linux-x86/bin/dalvikvm -Xbootclasspath:$DALVIK_VM_INIT_CLASS_PATH -cp foo.jar Foo
Hello, world
Using GDB like
gdb -args ./out/host/linux-x86/bin/dalvikvm -Xbootclasspath:$DALVIK_VM_INIT_CLASS_PATH -cp foo.jar Foo