2012-07-12 29 views
0

我想開發一個應用程序,我使用凹凸API。一切工作正常,第一次。不知何故,如果我按Home按鈕並回到應用程序它會崩潰沒有任何異常(有時它可以正常工作2或3次)。當我檢查我有以下堆棧跟蹤的logcat的:信號11(SIGSEGV),在android中使用凹凸API時的錯誤地址

16:33:18.915: I/DEBUG(31): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 
07-11 16:33:18.915: I/DEBUG(31): Build fingerprint: 'generic/sdk/generic/:2.2/FRF91/43546:eng/test-keys' 
07-11 16:33:18.915: I/DEBUG(31): pid: 280, tid: 338 >>> dig.app.com <<< 
07-11 16:33:18.915: I/DEBUG(31): signal 11 (SIGSEGV), fault addr 4897c000 
07-11 16:33:18.915: I/DEBUG(31): r0 4897bfe0 r1 4897bfe8 r2 ffecb094 r3 00000000 
07-11 16:33:18.915: I/DEBUG(31): r4 00000000 r5 00000000 r6 00000000 r7 00000000 
07-11 16:33:18.915: I/DEBUG(31): r8 00000000 r9 00000000 10 00000000 fp 00000000 
07-11 16:33:18.915: I/DEBUG(31): ip 00000000 sp 480cadf8 lr 00000010 pc afd0f234 cpsr a0000010 
07-11 16:33:19.025: I/DEBUG(31):   #00 pc 0000f234 /system/lib/libc.so 
07-11 16:33:19.061: W/dalvikvm(280): JNI WARNING: native code passing in bad object 0x4003fc78 0x4003fc78 (Check_SetFloatField) 
07-11 16:33:19.061: W/dalvikvm(280):    in Landroid/graphics 
/Path;.native_computeBounds (ILandroid/graphics/RectF;)V (SetFloatField) 
07-11 16:33:19.061: I/dalvikvm(280): "main" prio=5 tid=1 RUNNABLE 
07-11 16:33:19.061: I/dalvikvm(280): | group="main" sCount=0 dsCount=0 s=N obj=0x4001d8e0 self=0xccb0 
07-11 16:33:19.061: I/dalvikvm(280): | sysTid=280 nice=0 sched=0/0 cgrp=default handle=-1345026008 
07-11 16:33:19.061: I/dalvikvm(280): | schedstat=(955496474453 102439081045 208084) 
07-11 16:33:19.061: I/dalvikvm(280): at android.graphics.Path.native_computeBounds(Native Method) 
07-11 16:33:19.135: I/DEBUG(31):   #01 pc 00051e22 /data/data/dig.app.com/lib/libandroid-api.so 
07-11 16:33:19.135: I/DEBUG(31):   #02 pc 0005401a /data/data/dig.app.com/lib/libandroid-api.so 
07-11 16:33:19.135: I/DEBUG(31):   #03 pc 0005609e /data/data/dig.app.com/lib/libandroid-api.so 
07-11 16:33:19.135: I/DEBUG(31):   #04 pc 000512fe /data/data/dig.app.com/lib/libandroid-api.so 
07-11 16:33:19.135: I/DEBUG(31):   #05 pc 0001103c /system/lib/libc.so 
07-11 16:33:19.135: I/DEBUG(31):   #06 pc 00010b20 /system/lib/libc.so 
07-11 16:33:19.135: I/DEBUG(31): code around pc: 
07-11 16:33:19.135: I/DEBUG(31): afd0f214 e2522020 3a00004d e35c0018 0a000033 
07-11 16:33:19.135: I/DEBUG(31): afd0f224 e35c0008 0a000018 e491c004 e1a0400c 
07-11 16:33:19.135: I/DEBUG(31): afd0f234 e8b10fe0 f5d1f040 e2522020 2491c004 
07-11 16:33:19.135: I/DEBUG(31): afd0f244 e1833804 e1a04824 e1844805 e1a05825 
07-11 16:33:19.135: I/DEBUG(31): afd0f254 e1855806 e1a06826 e1866807 e1a07827 
07-11 16:33:19.145: I/DEBUG(31): code around lr: 
07-11 16:33:19.145: I/DEBUG(31): stack: 
07-11 16:33:19.145: I/DEBUG(31):  480cadb8 00000000 
07-11 16:33:19.145: I/DEBUG(31):  480cadbc 005cc628 [heap] 
07-11 16:33:19.145: I/DEBUG(31):  480cadc0 00000000 
07-11 16:33:19.145: I/DEBUG(31):  480cadc4 afd103f0 /system/lib/libc.so 
07-11 16:33:19.145: I/DEBUG(31):  480cadc8 00000003 
07-11 16:33:19.145: I/DEBUG(31):  480cadcc afd41724 /system/lib/libc.so 
07-11 16:33:19.145: I/DEBUG(31):  480cadd0 00562878 [heap] 
07-11 16:33:19.145: I/DEBUG(31):  480cadd4 c0000000 
07-11 16:33:19.145: I/DEBUG(31):  480cadd8 0007d0c4 [heap] 
07-11 16:33:19.145: I/DEBUG(31):  480caddc 0007d0c0 [heap] 
07-11 16:33:19.145: I/DEBUG(31):  480cade0 488470a1 
07-11 16:33:19.145: I/DEBUG(31):  480cade4 afd0c741 /system/lib/libc.so 
07-11 16:33:19.145: I/DEBUG(31):  480cade8 80a7cdd9 /data/data/dig.app.com/lib/libandroid-api.so 
07-11 16:33:19.145: I/DEBUG(31):  480cadec 005cc5e0 [heap] 
07-11 16:33:19.145: I/DEBUG(31):  480cadf0 df002777 
07-11 16:33:19.145: I/DEBUG(31):  480cadf4 e3a070ad 
07-11 16:33:19.145: I/DEBUG(31): #00 480cadf8 fffffffe 
07-11 16:33:19.145: I/DEBUG(31):  480cadfc 48847099 
07-11 16:33:19.145: I/DEBUG(31):  480cae00 480cae4c 
07-11 16:33:19.145: I/DEBUG(31):  480cae04 0007d0c4 [heap] 
07-11 16:33:19.155: I/DEBUG(31):  480cae08 0007d0c0 [heap] 
07-11 16:33:19.155: I/DEBUG(31):  480cae0c 488470a1 
07-11 16:33:19.155: I/DEBUG(31):  480cae10 00000002 
07-11 16:33:19.155: I/DEBUG(31):  480cae14 48847098 
07-11 16:33:19.155: I/DEBUG(31):  480cae18 48847008 
07-11 16:33:19.155: I/DEBUG(31):  480cae1c 80a51e25 /data/data/dig.app.com/lib/libandroid-api.so 
07-11 16:33:19.155: I/DEBUG(31): #01 480cae20 00000000 
07-11 16:33:19.155: I/DEBUG(31):  480cae24 480cae4c 

凸點API包含的本地庫到我的應用程序(libandroid-api.so)。爲了連接到凹凸服務器,我正在使用服務,並在onStop期間(當我按Home鍵時)我unbinding服務和在onStart(當從後臺恢復時)我會綁定服務。所以如果我繼續這個解除綁定和綁定2或3次,我得到這個錯誤。

我已經做了一些關於這個信號的搜索(SIGSEGV),故障地址,並發現它發生在應用程序產生無效的內存引用時。我沒有任何訪問這個本地庫。我不知道該怎麼辦。

回答

0

我有同樣的問題,事實是第一個api.configure工作正常,下一次嘗試只是崩潰的應用程序。

我貼什麼,我相信同樣的問題在這裏:Bump API Android crash

我解決我自己,我建周圍的凸起API單身,所以我確保API配置只是一個時間,然後它纔會返回一旦已經配置。你會在我的問題中找到代碼。

2

您應該只在每個應用程序上運行一次調用configure的單例。

相關問題