未解决

集成到cocos2dxActivity ,armeabi下同时有cocos的so文件,程序崩溃! #4137个回答

push_client_sdk_for_android 4.5.1 fengrmei 2015-07-16

问:
集成到程序后,测试了可以推送消息,但是不久后程序崩溃,现象是退出程序后会自动重启,提示:signal 11 (SIGSEGV),code 1 (SEGV_MAPERR),fault addr 00000024
确认 取消
答:
请问你解决的方式是?给其他开发者借鉴下。

云平台_李克 2015-07-17

答:
问题已经解决,谢谢~~~

fengrmei 2015-07-17

答:
手机是4.3,三星7106

fengrmei 2015-07-17

答:
第二个fatal: I/DEBUG (29026): !@dumpstate -k -t -z -d -o /data/log/dumpstate_app_native -m 5314 D/NativeCrashListener( 696): Closing socket connection: FileDescriptor[353] I/ActivityManager( 696): Notify an ApplicationCrash I/dumpstate( 5395): begin F/libc ( 5398): Fatal signal 13 (SIGPIPE) at 0x00001516 (code=0), thread 5398 (uptime) E/Sensors ( 696): Lightsensor values:6.000000 D/dalvikvm( 696): GC_FOR_ALLOC freed 1273K, 25% free 42526K/56128K, paused 135ms, total 135ms I/WindowManager( 696): Screenshot Window{42db7388 u0 com.xiaobanlong.main/com.xiaobanlong.main.Xiaobanlong} was all black! mSurfaceLayer=21030 minLayer=21025 maxLayer=21030 D/STATUSBAR-StatusBarManagerService( 696): manageDisableList what=0x0 pkg=WindowManager.LayoutParams E/Sensors ( 696): Lightsensor values:14.000000 E/android.os.Debug( 696): !@Dumpstate > dumpstate -k -t -z -d -o /data/log/dumpstate_app_error I/dumpstate( 5400): begin I/dumpstate( 5400): dumpstate is still running E/Sensors ( 696): Lightsensor values:14.000000 I/power ( 696): *** acquire_dvfs_lock : lockType : 1 freq : 1190400 D/SSRMv2:CustomFrequencyManagerService( 696): acquireDVFSLockLocked : type : DVFS_MIN_LIMIT frequency : 1190400 uid : 1000 pid : 696 pkgName : ACTIVITY_RESUME_BOOSTER@5 W/ActivityManager( 696): mDVFSHelper.acquire() D/WindowManager( 696): computeScreenConfigurationLocked() set config.orientation=1 dw=720 dh=1280 Callers=com.android.server.wm.WindowManagerService.updateOrientationFromAppTokensLocked:5181 com.android.server.wm.WindowManagerService.updateOrientationFromAppTokens:5152 com.android.server.am.ActivityStack.resumeTopActivityLocked:2785 D/PowerManagerService( 696): setKeyboardVisibility: false

fengrmei 2015-07-17

答:
第一个fatal: F/libc ( 5314): Fatal signal 11 (SIGSEGV) at 0x00000024 (code=1), thread 5341 (Thread-8102) I/DEBUG (29026): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** I/DEBUG (29026): Build fingerprint: 'samsung/ms013gzn/ms013g:4.3/JLS36C/G7106ZNUANG1:user/release-keys' I/DEBUG (29026): Revision: '7' I/DEBUG (29026): pid: 5314, tid: 5341, name: Thread-8102 >>> com.xiaobanlong.main <<< I/DEBUG (29026): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000024 E/Sensors ( 696): Lightsensor values:13.000000 D/SSRMv2:Monitor( 696): SIOP:: AP = 470, Prev AP = 460, Duration = 10397 W/ProcessStats( 696): Skipping unknown process pid 5363 W/ProcessStats( 696): Skipping unknown process pid 5364 W/ProcessStats( 696): Skipping unknown process pid 5374 W/ProcessStats( 696): Skipping unknown process pid 5383 E/Sensors ( 696): Lightsensor values:13.000000 I/DEBUG (29026): r0 00000000 r1 5fb4ca04 r2 61995008 r3 00000000 I/DEBUG (29026): r4 5f7e7b34 r5 44340000 r6 00000000 r7 5fa4cf30 I/DEBUG (29026): r8 5fb4cb38 r9 5fa4cf28 sl 5c2488a8 fp 5fb4c9e4 I/DEBUG (29026): ip 00000001 sp 5fb4c9a8 lr 5f209138 pc 5f2f4988 cpsr 20000010 I/DEBUG (29026): d0 74616d72416c6258 d1 3a68746150657275 I/DEBUG (29026): d2 6d696e41736d7261 d3 0a2f736e6f697461 I/DEBUG (29026): d4 3fb33dc61a93ea8e d5 0000000000000000 I/DEBUG (29026): d6 0000000000000000 d7 0103b7808800759c I/DEBUG (29026): d8 0000000000000000 d9 0000000000000000 I/DEBUG (29026): d10 0000000000000000 d11 0000000000000000 I/DEBUG (29026): d12 0000000000000000 d13 0000000000000000 I/DEBUG (29026): d14 0000000000000000 d15 0000000000000000 I/DEBUG (29026): d16 582f6c6278696e61 d17 65726665524e4c42 I/DEBUG (29026): d18 63735f77742f6970 d19 5f7261626c6c6f72 I/DEBUG (29026): d20 6c5f656c646e6168 d21 705f67625f746665 I/DEBUG (29026): d22 6c6f685f73736572 d23 392e6b7261645f6f I/DEBUG (29026): d24 3f6dcabc4571abc1 d25 3f30837711244472 I/DEBUG (29026): d26 3f4375429245411f d27 3f133abc51b768d7 I/DEBUG (29026): d28 3f1420ec8fb87f66 d29 bef375cbdb605373 I/DEBUG (29026): d30 3ff0000000000000 d31 3fd5555555555563 I/DEBUG (29026): scr 20000012 I/DEBUG (29026): I/DEBUG (29026): backtrace: I/DEBUG (29026): #00 pc 00b88988 /data/app-lib/com.xiaobanlong.main-15/libcocos2dcpp.so (cocos2d::Scheduler::schedulePerFrame(std::function<void (float)> const&, void*, int, bool)+48) I/DEBUG (29026): #01 pc 00a9d134 /data/app-lib/com.xiaobanlong.main-15/libcocos2dcpp.so (void cocos2d::Scheduler::scheduleUpdate<cocos2d::Node>(cocos2d::Node*, int, bool)+100) I/DEBUG (29026):

fengrmei 2015-07-17

答:
日志如下,第一个fatal造成程序频繁重启,应该和cocos有关,但是把百度推送的代码屏蔽后,程序是正常的;第二个fatal时程序会弹出"程序已停止"的错误对话框:

fengrmei 2015-07-17

答:
能提供下详细的错误信息嘛,最好有重现的步奏,手机版本,型号。

云平台_李克 2015-07-16