碰到Fatal signal 11 (SIGSEGV)，求解答 - Android当前位置:& &&&碰到Fatal signal 11 (SIGSEGV)，求解答碰到Fatal signal 11 (SIGSEGV)，求解答&&网友分享于：&&浏览：84次遇到Fatal signal 11 (SIGSEGV)，求解答本帖最后由 u 于
14:51:16 编辑
最近遇到个坑爹的问题，看下面的logcat：04-02&02:17:31.777:&D/dalvikvm(1405):&Trying&to&load&lib&/data/data/com.novonity.uchat/lib/libutils_armv5te.so&0x
04-02&02:17:31.827:&D/dalvikvm(1405):&Added&shared&lib&/data/data/com.novonity.uchat/lib/libutils_armv5te.so&0x
04-02&02:17:31.898:&D/dalvikvm(1405):&No&JNI_OnLoad&found&in&/data/data/com.novonity.uchat/lib/libutils_armv5te.so&0x,&skipping&init
04-02&02:17:31.937:&D/org.doubango.ngn.NgnEngine(1405):&CPU_Feature=15
04-02&02:17:31.937:&D/org.doubango.ngn.NgnEngine(1405):&isCpuNeon()=YES
04-02&02:17:31.937:&D/dalvikvm(1405):&Trying&to&load&lib&/data/data/com.novonity.uchat/lib/libtinyWRAP_armv7-a.so&0x
04-02&02:17:31.997:&A/libc(1405):&Fatal&signal&11&(SIGSEGV)&at&0xdeadbaad&(code=1),&thread&1405&(.novonity.uchat)
以上logcat是在4.3的模拟器上测试的，会闪退，再看以下logcat：04-02&14:27:13.926:&D/dalvikvm(28586):&Trying&to&load&lib&/data/data/com.novonity.uchat/lib/libutils_armv5te.so&0x41fa4c40
04-02&14:27:13.926:&D/dalvikvm(28586):&Added&shared&lib&/data/data/com.novonity.uchat/lib/libutils_armv5te.so&0x41fa4c40
04-02&14:27:13.926:&D/dalvikvm(28586):&No&JNI_OnLoad&found&in&/data/data/com.novonity.uchat/lib/libutils_armv5te.so&0x41fa4c40,&skipping&init
04-02&14:27:13.936:&D/org.doubango.ngn.NgnEngine(28586):&CPU_Feature=15
04-02&14:27:13.936:&D/org.doubango.ngn.NgnEngine(28586):&isCpuNeon()=YES
04-02&14:27:13.936:&D/dalvikvm(28586):&Trying&to&load&lib&/data/data/com.novonity.uchat/lib/libtinyWRAP_armv7-a.so&0x41fa4c40
04-02&14:27:13.946:&W/linker(28586):&libtinyWRAP_armv7-a.so&has&text&relocations.&This&is&wasting&memory&and&is&a&security&risk.&Please&fix.
04-02&14:27:13.946:&D/dalvikvm(28586):&Added&shared&lib&/data/data/com.novonity.uchat/lib/libtinyWRAP_armv7-a.so&0x41fa4c40
04-02&14:27:13.946:&D/dalvikvm(28586):&No&JNI_OnLoad&found&in&/data/data/com.novonity.uchat/lib/libtinyWRAP_armv7-a.so&0x41fa4c40,&skipping&init
这个是在Nexus&7上测试的logcat，经过我多个版本测试，结果是4.4，4.4.2，4.2.1，2.3.6等几个版本可以运行，在个别比如4.3版本上会出现：Fatal&signal&11&(SIGSEGV)&at&0xdeadbaad&(code=1),&thread&1405&(.novonity.uchat)并且，可以运行的版本不管模拟器或真机都可以，不能运行的不管模拟器还是真机都会闪退，估计是libtinyWRAP_armv7-a.so有问题，但是是什么问题，没搞懂，谁帮忙解答一下------解决方案--------------------你的动态链接库有问题&换一个就可以了。
12345678910
12345678910
12345678910 上一篇：下一篇：文章评论相关解决方案 12345678910 Copyright & &&版权所有遇到Fatal signal 11 (S-中国学网-中国IT综合门户网站-提供健康,养生,留学,移民,创业,汽车等信息
> 信息中心 >
遇到Fatal signal 11 (S
来源：互联网 发表时间： 17:39:30 责任编辑：王亮字体：
为了帮助网友解决“遇到Fatal signal 11 (S”相关的问题，中国学网通过互联网对“遇到Fatal signal 11 (S”相关的解决方案进行了整理,用户详细问题包括:本帖最后由 u 于
14:51:16 编辑测试Fatal?signaljava最近遇到个坑爹的问题，看下面的logcat：04-02&02:17:31.777:&D/dalvikvm(1405):&Trying&to&load&lib&/data/data/com.novonity.uchat/lib/libutils_armv5te.so&0x04-02&02:17:31.827:&D/dalvikvm(1405):&Added&shared&lib&/data/data/com.novonity.uchat/lib/libutils_armv5te.so&0x04-02&02:17:31.898:&D/dalvikvm(1405):&No&JNI_OnLoad&found&in&/data/data/com.novonity.uchat/lib/libutils_armv5te.so&0x,&skipping&init04-02&02:17:31.937:&D/org.doubango.ngn.NgnEngine(1405):&CPU_Feature=1504-02&02:17:31.937:&D/org.doubango.ngn.NgnEngine(1405):&isCpuNeon()=YES04-02&02:17:31.937:&D/dalvikvm(1405):&Trying&to&load&lib&/data/data/com.novonity.uchat/lib/libtinyWRAP_armv7-a.so&0x04-02&02:17:31.997:&A/libc(1405):&Fatal&signal&11&(SIGSEGV)&at&0xdeadbaad&(code=1),&thread&1405&(.novonity.uchat)以上logcat是在4.3的模拟器上测试的，会闪退，再看以下logcat：04-02&14:27:13.926:&D/dalvikvm(28586):&Trying&to&load&lib&/data/data/com.novonity.uchat/lib/libutils_armv5te.so&0x41fa4c4004-02&14:27:13.926:&D/dalvikvm(28586):&Added&shared&lib&/data/data/com.novonity.uchat/lib/libutils_armv5te.so&0x41fa4c4004-02&14:27:13.926:&D/dalvikvm(28586):&No&JNI_OnLoad&found&in&/data/data/com.novonity.uchat/lib/libutils_armv5te.so&0x41fa4c40,&skipping&init04-02&14:27:13.936:&D/org.doubango.ngn.NgnEngine(28586):&CPU_Feature=1504-02&14:27:13.936:&D/org.doubango.ngn.NgnEngine(28586):&isCpuNeon()=YES04-02&14:27:13.936:&D/dalvikvm(28586):&Trying&to&load&lib&/data/data/com.novonity.uchat/lib/libtinyWRAP_armv7-a.so&0x41fa4c4004-02&14:27:13.946:&W/linker(28586):&libtinyWRAP_armv7-a.so&has&text&relocations.&This&is&wasting&memory&and&is&a&security&risk.&Please&fix.04-02&14:27:13.946:&D/dalvikvm(28586):&Added&shared&lib&/data/data/com.novonity.uchat/lib/libtinyWRAP_armv7-a.so&0x41fa4c4004-02&14:27:13.946:&D/dalvikvm(28586):&No&JNI_OnLoad&found&in&/data/data/com.novonity.uchat/lib/libtinyWRAP_armv7-a.so&0x41fa4c40,&skipping&init这个是在Nexus&7上测试的logcat，经过我多个版本测试，结果是4.4，4.4.2，4.2.1，2.3.6等几个版本可以运行，在个别比如4.3版本上会出现：Fatal&signal&11&(SIGSEGV)&at&0xdeadbaad&(code=1),&thread&1405&(.novonity.uchat)并且，可以运行的版本不管模拟器或真机都可以，不能运行的不管模拟器还是真机都会闪退，估计是libtinyWRAP_armv7-a.so有问题，但是是什么问题，没搞懂，谁帮忙解答一下，具体解决方案如下：解决方案1：不兼容。中国学网
解决方案2：Fatal&signal&11&(SIGSEGV)&at&0xdeadbaad&(code=1),&thread&1405&(.novonity.uchat)应该是JNI代码的问题，0xdeadbaad&这个地址一般用于标识一个被free掉的指针可以编译一个debug的so库，然后等崩溃后看一下调用堆栈解决方案3：引用&2&楼&youngc527&的回复:Fatal&signal&11&(SIGSEGV)&at&0xdeadbaad&(code=1),&thread&1405&(.novonity.uchat)应该是JNI代码的问题，0xdeadbaad&这个地址一般用于标识一个被free掉的指针可以编译一个debug的so库，然后等崩溃后看一下调用堆栈跟内存有关系么？解决方案4：你的动态链接库有问题&换一个就可以了。解决方案5：引用&3&楼&u&的回复:Quote: 引用&2&楼&youngc527&的回复:Fatal&signal&11&(SIGSEGV)&at&0xdeadbaad&(code=1),&thread&1405&(.novonity.uchat)应该是JNI代码的问题，0xdeadbaad&这个地址一般用于标识一个被free掉的指针可以编译一个debug的so库，然后等崩溃后看一下调用堆栈跟内存有关系么？一般是代码写的有问题，比如说unsigned&char&*buffer&=&malloc(1024);...free(buffer);buffer&=&0//&为了表示这个指针已经被free了，通常会把它设置成一个特殊的值，比如&0xdeadbaadstrcpy(buffer,&"Fatal&:(");//&执行这句就会导致Fatal错误解决方案6：楼主解决没,我也遇到这操蛋的问题了,光在百度地图相关的类上报这个Fatal&11&code&1解决方案7：引用&6&楼&shenshibaoma&的回复:楼主解决没,我也遇到这操蛋的问题了,光在百度地图相关的类上报这个Fatal&11&code&1我也是经常遇到,&尤其是在安卓4上面,&看来只能等百度地图SDK更新了(3.0.0没试过,&反正2.3.x到2.4.2都不行)...&也可能是定位SDK&3.x的问题解决方案8：我在4.3上用OpenCV也遇到了类似问题：A/libc(21897):&Fatal&signal&11&(SIGSEGV)&at&0x0000010a&(code=1),&thread&22103&(Thread-1068)@youngc527&,兄台帮忙看下这个应该是什么出啦问题？我在jni中创建一个对象，把指针保存起来传回java下（long型），再连同要处理的图片传回jni下，通过该指针去构造一个训练模型，再预测，然后就挂了。解决方案9：我训练load的这个xml文件大小为3031k。我检验过，第二次传回的指针和我保存在jni下的全局指针是相同的。JNIEXPORT&jint&JNICALL&Java_com_example_affectiverecognizer_AffRecog_Predict(JNIEnv&*jenv,&jclass,&jlong&thiz,&jintArray&jtestImage,&jint&jwidth,&jint&jheight){&&&&jint&result&=&0;&&&&if&(GlobalModelPointer&!=&(FaceRecognizer*)thiz){&&&&&&&CV_Error(CV_StsBadArg,&"error&in&transport&facerognizer&pointer");&&&&}Ptr&FaceRecognizer&&model((FaceRecognizer*)thiz);//&&&&//try&reload&file//&&&&Ptr&FaceRecognizer&&newModel&=&createFisherFaceRecognizer();//&&&&newModel-&load("/data/data/com.example.affectiverecognizer/app_fishermodel/fisher_model_xm.xml");&&&&jint&*ptestI&&&&ptestImage&=&jenv-&GetIntArrayElements(jtestImage,&false);&&&&if(ptestImage&==&NULL){&&&&return&-1;&&&&}&&&&Mat&testImage(jheight,&jwidth,&CV_8UC1,&(unsigned&char*)ptestImage);result&=&model-&predict(testImage);model.release();return&}
相关文章：
最新添加资讯
24小时热门资讯
Copyright © 2004- All Rights Reserved. 中国学网 版权所有
京ICP备号-1 京公网安备02号17:07:53 UTC
I’m developing an application for Android using cocos2d-x. I’m new to cocos2d-x and C*+ and I’m on windows, I have followed due process from creating the Cocos2d-x project template for Eclipse to importing the project into Eclipse and adding c*+ features to it etc… I succesfully got my app to run in the emulator(target API 4.1) and it gives me the cocos2d “HelloWorld Splash” as expected. Problem is, now I’m trying to change my Application background image. I added an image in the assets directory and changed the code in “HelloWorldScene.cpp” that creates the default HelloWorld Sprite
CCSprite* pSprite = CCSprite::create(“HelloWorld.png”);
CCSprite* pSprite = CCSprite::create(“background.jpg”);
Once I do the latter, my emulator crashes after trying to run the App and in logcat I get the error “Fatal signal 11 (SIGSEGV) at 0x (code=1)”, but if I put back the default HelloWorld.png it runs again smoothly in the emulator.
I use cocos2d-2.0-rc2-x-2.0.1 and android-ndk-r8b. This App runs only on a 4.1 API device emulator, I can’t get it to run on 2.3.3 and 4.3 as it crashes while trying to run. Please, kindly help me out please
17:49:40 UTC
Be sure to check the spelling of your file(case-sensitive), if your file is “Background.jpg” and you place “background.jpg” in your code, CCPSprite will fail to load the file and throw an error.
11:52:22 UTC
Thanks for the response, but it’s not the spelling. It’s probably something else I’m yet to find out about
14:10:42 UTC
Try refreshing Eclipse to make sure that your .jpg file is absolutely, positively included in the apk bundle (right click project-&refresh). Also try a .png… perhaps your Android implementation trips up on that particular type of jpg?
16:13:09 UTC
Got this reply from a friend, it worked flawlessly:
what cocos2d-x did is, it compiles your c*+ code to a java library first, and put it into the libs/arm-v7s folder, then it use the eclipse build to build this library with assets together to the apk file. once you edit the c*+ file, you have to rebuild the libgame.so. There should be a script sits in android project folder named build_native.sh, you can run it using cygwin(windows) or just run it under Mac. this script will rebuild the source code to library and update assets folder according to whatever you put in the Resources folder
16:21:02 UTC
Ah yes, you’ll be running that script a lot as you build stuff for Android.