JNI配置问题
2016-02-16 14:52
148 查看
在开发版本中,我们通常打开的jni检查选项,(ro.kernel.android.checkjni= 1),
如果安装的apk不是理智的(不是非常吻合JNI接口的),虚拟机会报出:这不是有效的JNI引用,就会导致虚拟机崩溃,导致apk停止
for the development, we usually open the jni check option (ro.kernel.android.checkjni=1). if the apk native code is not every sanity, vm will tell you that
"it's not a valid jni reference" and cause a dalvik crash to stop the apk.
nasty log msg:
09-05 10:24:16.129 W/dalvikvm( 1423): JNI WARNING: 0x417d73f8 is not a valid JNI reference
09-05 10:24:16.129 W/dalvikvm( 1423): in Lcom/zeptolab/ctr/CtrRenderer;.nativeTick:(J)V (GetObjectClass)
09-05 10:24:16.129 I/dalvikvm( 1423): "GLThread 183" prio=5 tid=26 RUNNABLE
09-05 10:24:16.129 I/dalvikvm( 1423): | group="main" sCount=0 dsCount=0 obj=0x41d1e4e8 self=0x19b8d40
09-05 10:24:16.129 I/dalvikvm( 1423): | sysTid=1479 nice=0 sched=0/0 cgrp=default handle=28663136
09-05 10:24:16.129 I/dalvikvm( 1423): | schedstat=( 0 0 0 ) utm=1547 stm=267 core=0
09-05 10:24:16.129 I/dalvikvm( 1423): at com.zeptolab.ctr.CtrRenderer.nativeTick(Native Method)
09-05 10:24:16.129 I/dalvikvm( 1423): at com.zeptolab.ctr.CtrRenderer.onDrawFrame(CtrRenderer.java:424)
09-05 10:24:16.129 I/dalvikvm( 1423): at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1470)
09-05 10:24:16.129 I/dalvikvm( 1423): at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1217)
09-05 10:24:16.129 I/dalvikvm( 1423):
09-05 10:24:16.129 E/dalvikvm( 1423): VM aborting
09-05 10:24:16.139 F/libc ( 1423): Fatal signal 11 (SIGSEGV) at 0xdeadd00d (code=1)
09-05 10:24:16.639 I/DEBUG ( 141): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
09-05 10:24:16.639 I/DEBUG ( 141): pid: 1423, tid: 1479 >>> com.zeptolab.ctr.lite.google <<<
09-05 10:24:16.639 I/DEBUG ( 141): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadd00d
如果安装的apk不是理智的(不是非常吻合JNI接口的),虚拟机会报出:这不是有效的JNI引用,就会导致虚拟机崩溃,导致apk停止
for the development, we usually open the jni check option (ro.kernel.android.checkjni=1). if the apk native code is not every sanity, vm will tell you that
"it's not a valid jni reference" and cause a dalvik crash to stop the apk.
nasty log msg:
09-05 10:24:16.129 W/dalvikvm( 1423): JNI WARNING: 0x417d73f8 is not a valid JNI reference
09-05 10:24:16.129 W/dalvikvm( 1423): in Lcom/zeptolab/ctr/CtrRenderer;.nativeTick:(J)V (GetObjectClass)
09-05 10:24:16.129 I/dalvikvm( 1423): "GLThread 183" prio=5 tid=26 RUNNABLE
09-05 10:24:16.129 I/dalvikvm( 1423): | group="main" sCount=0 dsCount=0 obj=0x41d1e4e8 self=0x19b8d40
09-05 10:24:16.129 I/dalvikvm( 1423): | sysTid=1479 nice=0 sched=0/0 cgrp=default handle=28663136
09-05 10:24:16.129 I/dalvikvm( 1423): | schedstat=( 0 0 0 ) utm=1547 stm=267 core=0
09-05 10:24:16.129 I/dalvikvm( 1423): at com.zeptolab.ctr.CtrRenderer.nativeTick(Native Method)
09-05 10:24:16.129 I/dalvikvm( 1423): at com.zeptolab.ctr.CtrRenderer.onDrawFrame(CtrRenderer.java:424)
09-05 10:24:16.129 I/dalvikvm( 1423): at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1470)
09-05 10:24:16.129 I/dalvikvm( 1423): at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1217)
09-05 10:24:16.129 I/dalvikvm( 1423):
09-05 10:24:16.129 E/dalvikvm( 1423): VM aborting
09-05 10:24:16.139 F/libc ( 1423): Fatal signal 11 (SIGSEGV) at 0xdeadd00d (code=1)
09-05 10:24:16.639 I/DEBUG ( 141): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
09-05 10:24:16.639 I/DEBUG ( 141): pid: 1423, tid: 1479 >>> com.zeptolab.ctr.lite.google <<<
09-05 10:24:16.639 I/DEBUG ( 141): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadd00d
相关文章推荐
- URAL 1820. Ural Steaks(数学啊 )
- leetcode 258. Add Digits
- 判断点是否在三角形内
- 快速掌握Node.js环境的安装与运行方法
- cron - 定时清空超过30天的文件
- 试用android studio
- Android图片圆角 用简单的方法实现
- K3无界面登录新增职员
- 蓝牙手柄按键码
- IOS-关于IAP:苹果的审核规则发生了一点变化--没有“Restore”将会被拒
- jacoco测试覆盖率maven配置
- CyclicBarrier
- RoboBinding:一个实现了数据绑定 Presentation Model(MVVM) 模式的Android开源框架
- NSInvocation简单用法
- winform treeView 数据绑定
- C++string的replace函数
- Youtube800万美元BandPage
- Redis缓存数据库
- 与splash详解相关的
- Protractor