昨天遇到个dexopt失败的奇怪问题，记录一下

昨天写个应用，push到系统中，不能被识别安装了应用，重启后桌面会出现图标，但是点击就会运行失败，log如下

E/dalvikvm( 2114): Bogus handler offset: 0x4
E/dalvikvm( 2114): Trouble with item 108 @ offset 0x3f9f4
E/dalvikvm( 2114): Swap of section type 2001 failed
E/dalvikvm( 2114): ERROR: Byte swap + verify failed
D/PowerManagerService(  290): onSensorChanged: light value: 38, mHighestLightSensorValue:-1
D/PowerManagerService(  290): lcdValue == mLightSensorScreenBrightnessWait, do nothing
E/LiZhao  ( 1322): **** getExternalStorageDirectory value = 0
E/dalvikvm( 2114): Optimization failed
W/installd(  120): DexInv: --- END '/system/app/SuperPowerSave.apk' --- status=0xff00, process failed
E/installd(  120): dexopt failed on '/data/dalvik-cache/system@app@SuperPowerSave.apk@classes.dex' res = 65280
D/PowerManagerService(  290): setKeyboardVisibility: false
V/ActivityManager(  290): ACT-Launching: ActivityRecord{42b6b788 com.cly.SuperPowerSave/.SuperPowerSaveActivity}
D/NetworkPolicy(  290): onRecv: MSG_FOREGROUND_ACTIVITIES_CHANGED pid:uid:act=2100:1000:true
D/ActivityManager(  290): ACT-AM_RESTART_ACTIVITY ActivityRecord{42b6b788 com.cly.SuperPowerSave/.SuperPowerSaveActivity} Task:11
I/PackageManager(  290): Running dexopt on: com.cly.SuperPowerSave
D/dalvikvm( 2115): threadid=1: interp stack at 0x433cd000
D/PowerManagerService(  290): onSensorChanged: light value: 46, mHighestLightSensorValue:-1
D/PowerManagerService(  290): lcdValue == mLightSensorScreenBrightnessWait, do nothing
E/dalvikvm( 2115): Bogus handler offset: 0x4
E/dalvikvm( 2115): Trouble with item 108 @ offset 0x3f9f4
E/dalvikvm( 2115): Swap of section type 2001 failed
E/dalvikvm( 2115): ERROR: Byte swap + verify failed
D/PowerManagerService(  290): onSensorChanged: light value: 52, mHighestLightSensorValue:-1
D/PowerManagerService(  290): lcdValue == mLightSensorScreenBrightnessWait, do nothing
E/dalvikvm( 2115): Optimization failed
W/installd(  120): DexInv: --- END '/system/app/SuperPowerSave.apk' --- status=0xff00, process failed
E/installd(  120): dexopt failed on '/data/dalvik-cache/system@app@SuperPowerSave.apk@classes.dex' res = 65280
V/WindowManager(  290): Changing focus from Window{41967ae0 com.cly.launcher2/com.cly.launcher2.Launcher paused=false} to null
D/color   (  461): ----------------------------- res = 0
I/WindowManager(  290): Losing focus: Window{41967ae0 com.cly.launcher2/com.cly.launcher2.Launcher paused=false}
V/ActivityManager(  290): getTasks: max=1, flags=0, receiver=null
V/ActivityManager(  290): com.cly.SuperPowerSave/.SuperPowerSaveActivity: task=TaskRecord{42b6bd70 #11 A com.cly.SuperPowerSave}
V/ActivityManager(  290): We have pending thumbnails: null
I/SurfaceFlinger(  113): [SurfaceFlinger] frames:25, duration:1.516000, fps:16.485920
I/SurfaceTexture(  113): [com.cly.launcher2/com.cly.launcher2.Launcher(0x3c3168)] disconnect: api=2
D/dalvikvm( 2100): DexOpt: --- BEGIN 'SuperPowerSave.apk' (bootstrap=0) ---
D/dalvikvm( 2116): threadid=1: interp stack at 0x4311f000
E/dalvikvm( 2116): Bogus handler offset: 0x4
E/dalvikvm( 2116): Trouble with item 108 @ offset 0x3f9f4
E/dalvikvm( 2116): Swap of section type 2001 failed
E/dalvikvm( 2116): ERROR: Byte swap + verify failed

最好搞了半天，回退代码，发现一个函数很长导致了这个问题，将这个函数屏蔽掉，没有问题；后面分成两个函数些，有问题；再屏蔽其中一个又没问题；最后分成三个函数写，就没有问题了。觉得非常奇怪，记录下来，后续参考。如果有走过路过的大神知道原因，也请不吝赐教！在此先行谢过。

自己在网上找了两篇文章，这里摘录一下：

第一篇，原文：http://www.open-open.com/lib/view/open1327556525374.html

  android应用程序管理主要由PackageManager这个类来管理，实现PackageManager这个抽象类的是ContextImpl.java。在ContextImpl.java中，有一个内部静态类叫ApplicationPackageManager，实现了所有PackageManager的接口。

1	static final class ApplicationPackageManager extends PackageManager {

2

3	..........

4

5

｝

ApplicationPackageManager又是通过对IPackageManager封装调用，来实现的。

01	public PackageInfo getPackageInfo(String packageName, int flags)

02	throws NameNotFoundException {

03

try {

04	PackageInfo pi = mPM.getPackageInfo(packageName, flags);

05	if (pi != null) {

06	return pi;

07

}

08	} catch (RemoteException e) {

09	throw new RuntimeException("Package manager has died", e);

10

}

11

12	throw new NameNotFoundException(packageName);

13

}

这里的mPM就是IPackageManager，PackageManagerService就是对IPackageManager的实现。所以我们平时对PackageManager的调用，最终是的在PackageManagerService.java中实现的。在PackageManagerService.java每个方法的实现。

PackageManagerService启动流程：

PackageManagerService(context, factoryTest)是包管理服务的主进程。它完成了对/system/app,/data/app,/system/framework,/data/app-private下的apk文件的解析。详细流程如下：

1.建立java层的installer与c层的installd的socket联接，使得在上层的install,remove,dexopt等功能最终由installd在底层实现

2.建立PackageHandler消息循环，用于处理外部的apk安装请求消息，如adb install,packageinstaller安装apk时会发送消息

3.解析/system/etc/permission下xml文件(framework/base/data/etc/)，包括platform.xml和系统支持的各种硬件模块的feature.主要工作：

(1)建立底层user ids和group ids 同上层permissions之间的映射；可以指定一个权限与几个组ID对应。当一个