当前位置: 代码迷 >> Android >> 帮忙分析一下原因解决办法
  详细解决方案

帮忙分析一下原因解决办法

热度:121   发布时间:2016-05-01 21:54:40.0
帮忙分析一下原因
现象:模拟器启动时一直停在显示android那几个字样不动.
logcat之后得到以下内容:

D/AndroidRuntime( 403): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime( 403): CheckJNI is ON
I/dalvikvm( 403): DexOpt: mismatch dep signature for '/system/framework/framework.odex'
E/dalvikvm( 403): /system/framework/android.policy.jar odex has stale dependencies
I/dalvikvm( 403): Zip is good, but no classes.dex inside, and no valid .odex file in the same directory
D/dalvikvm( 403): Unable to process classpath element '/system/framework/android.policy.jar'
I/dalvikvm( 403): DexOpt: Some deps went away
E/dalvikvm( 403): /system/framework/services.jar odex has stale dependencies
I/dalvikvm( 403): Zip is good, but no classes.dex inside, and no valid .odex file in the same directory
D/dalvikvm( 403): Unable to process classpath element '/system/framework/services.jar'
I/dalvikvm( 403): DexOpt: mismatch dep signature for '/system/framework/framework.odex'
E/dalvikvm( 403): /system/framework/apache-xml.jar odex has stale dependencies
I/dalvikvm( 403): Zip is good, but no classes.dex inside, and no valid .odex file in the same directory
D/dalvikvm( 403): Unable to process classpath element '/system/framework/apache-xml.jar'
I/dalvikvm( 403): DexOpt: mismatch dep signature for '/system/framework/framework.odex'
E/dalvikvm( 403): /system/framework/filterfw.jar odex has stale dependencies
I/dalvikvm( 403): Zip is good, but no classes.dex inside, and no valid .odex file in the same directory
D/dalvikvm( 403): Unable to process classpath element '/system/framework/filterfw.jar'
E/JNIHelp ( 403): Native registration unable to find class 'com/android/server/Watchdog', aborting
F/libc ( 403): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
I/DEBUG ( 33): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 33): Build fingerprint: 'Android/full/generic:4.0.1/ITL41D/eng.arthur.20111222.154959:eng/test-keys'
I/DEBUG ( 33): pid: 403, tid: 403 >>> zygote <<<
I/DEBUG ( 33): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadbaad
I/DEBUG ( 33): r0 deadbaad r1 00000001 r2 a0000000 r3 00000000
I/DEBUG ( 33): r4 00000000 r5 00000027 r6 0000f2c0 r7 00000001
I/DEBUG ( 33): r8 4018f678 r9 40178fe2 10 00009040 fp 00009050
I/DEBUG ( 33): ip ffffffff sp bea66a90 lr 4001f121 pc 4001b880 cpsr 60000030
I/DEBUG ( 33): d0 3f4000003f400000 d1 0000000000000000
I/DEBUG ( 33): d2 0000000000000000 d3 0000000000000000
I/DEBUG ( 33): d4 0000000000000000 d5 41c3f44320000000
I/DEBUG ( 33): d6 3f50624dd2f1a9fc d7 000000003f800000
I/DEBUG ( 33): d8 0000000000000000 d9 0000000000000000
I/DEBUG ( 33): d10 0000000000000000 d11 0000000000000000
I/DEBUG ( 33): d12 0000000000000000 d13 0000000000000000
I/DEBUG ( 33): d14 0000000000000000 d15 0000000000000000
I/DEBUG ( 33): scr 60000010
I/DEBUG ( 33): 
I/DEBUG ( 33): #00 pc 00017880 /system/lib/libc.so
I/DEBUG ( 33): #01 pc 0000c282 /system/lib/libnativehelper.so (jniRegisterNativeMethods)
I/DEBUG ( 33): #02 pc 000413d8 /system/lib/libandroid_runtime.so (_ZN7android14AndroidRuntime21registerNativeMethodsEP7_JNIEnvPKcPK15JNINativeMethodi)
I/DEBUG ( 33): #03 pc 00070804 /system/lib/libandroid_runtime.so (_ZN7android32register_android_server_WatchdogEP7_JNIEnv)
I/DEBUG ( 33): #04 pc 000414e4 /system/lib/libandroid_runtime.so
I/DEBUG ( 33): #05 pc 00041516 /system/lib/libandroid_runtime.so (_ZN7android14AndroidRuntime8startRegEP7_JNIEnv)
I/DEBUG ( 33): #06 pc 0004160c /system/lib/libandroid_runtime.so (_ZN7android14AndroidRuntime5startEPKcS2_)
I/DEBUG ( 33): #07 pc 00008f0e /system/bin/app_process
  相关解决方案