什么可能导致Android的这个错误? [英] What might cause this error in android?
问题描述
我开发一个Android应用程序,我得到了2-5mins后,我公司推出的应用程序此错误。 这是什么?
I am developing an Android app and I got this error after 2-5mins I launched the application. What is this?
05-26 18:51:08.137: INFO/DEBUG(2894): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
05-26 18:51:08.137: INFO/DEBUG(2894): Build fingerprint: 'google/passion_kt/passion:2.3.3/GRI40/49208:user/release-keys'
05-26 18:51:08.137: INFO/DEBUG(2894): pid: 2956, tid: 2956 >>> com.company.app.p2p <<<
05-26 18:51:08.137: INFO/DEBUG(2894): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 45088dbc
05-26 18:51:08.137: INFO/DEBUG(2894): r0 42089000 r1 ffffffff r2 00000000 r3 ffffffff
05-26 18:51:08.137: INFO/DEBUG(2894): r4 20000000 r5 e8001200 r6 40009228 r7 00000001
05-26 18:51:08.137: INFO/DEBUG(2894): r8 4051a3f8 r9 800a5600 10 80000000 fp 00000001
05-26 18:51:08.137: INFO/DEBUG(2894): ip 00bfff6f sp beb28d08 lr 80036028 pc 80035938 cpsr a0000010
05-26 18:51:08.137: INFO/DEBUG(2894): d0 0000000000056b17 d1 6c675f6c6c6f7200
05-26 18:51:08.137: INFO/DEBUG(2894): d2 6d6172662f6d6528 d3 72662f6b726f7707
05-26 18:51:08.137: INFO/DEBUG(2894): d4 0000000000000000 d5 0000000000000000
05-26 18:51:08.137: INFO/DEBUG(2894): d6 0000000000000000 d7 4080000000000000
05-26 18:51:08.137: INFO/DEBUG(2894): d8 0000a27fb5b4b66f d9 4325d5f141400000
05-26 18:51:08.137: INFO/DEBUG(2894): d10 4269198840557fe0 d11 0000000042391988
05-26 18:51:08.137: INFO/DEBUG(2894): d12 0000000000000000 d13 0000000000000000
05-26 18:51:08.137: INFO/DEBUG(2894): d14 0000000000000000 d15 0000000000000000
05-26 18:51:08.137: INFO/DEBUG(2894): d16 002b09c8000000a0 d17 bff0000000000000
05-26 18:51:08.137: INFO/DEBUG(2894): d18 3ff0000000000000 d19 0000000000000000
05-26 18:51:08.137: INFO/DEBUG(2894): d20 0000000000000000 d21 0000000000000000
05-26 18:51:08.137: INFO/DEBUG(2894): d22 3ff0000000000000 d23 0000000000000000
05-26 18:51:08.137: INFO/DEBUG(2894): d24 3ff0000000000000 d25 0000000000000000
05-26 18:51:08.137: INFO/DEBUG(2894): d26 0000000000000000 d27 0000000000000000
05-26 18:51:08.137: INFO/DEBUG(2894): d28 0100010001000100 d29 3ff8000000000000
05-26 18:51:08.137: INFO/DEBUG(2894): d30 0000000000000000 d31 3fe5555555555555
05-26 18:51:08.137: INFO/DEBUG(2894): scr 60000012
05-26 18:51:08.207: INFO/DEBUG(2894): #00 pc 00035938 /system/lib/libdvm.so
05-26 18:51:08.207: INFO/DEBUG(2894): #01 pc 00036024 /system/lib/libdvm.so
05-26 18:51:08.207: INFO/DEBUG(2894): #02 pc 000368cc /system/lib/libdvm.so
05-26 18:51:08.207: INFO/DEBUG(2894): #03 pc 00020350 /system/lib/libdvm.so
05-26 18:51:08.207: INFO/DEBUG(2894): code around pc:
05-26 18:51:08.207: INFO/DEBUG(2894): 80035918 e065c003 e1530007 85803010 e5900000
05-26 18:51:08.207: INFO/DEBUG(2894): 80035928 e1e051ac e1a0c42c e205701f e1a0771b
05-26 18:51:08.207: INFO/DEBUG(2894): 80035938 e790510c e1170005 e1875005 e780510c
05-26 18:51:08.207: INFO/DEBUG(2894): 80035948 1a00000c e5960014 e1530000 35960008
05-26 18:51:08.207: INFO/DEBUG(2894): 80035958 3240c004 3586c008 35003004 e59d3004
05-26 18:51:08.207: INFO/DEBUG(2894): code around lr:
05-26 18:51:08.207: INFO/DEBUG(2894): 80036008 0a000001 e3a02000 eb014474 e596209c
05-26 18:51:08.207: INFO/DEBUG(2894): 80036018 eaffffd1 e1a01005 e1a00006 ebfffe1c
05-26 18:51:08.207: INFO/DEBUG(2894): 80036028 e596102c e3510001 d8bd87f0 e5962058
05-26 18:51:08.207: INFO/DEBUG(2894): 80036038 e3520000 d8bd87f0 e3a04000 e3a0a001
05-26 18:51:08.207: INFO/DEBUG(2894): 80036048 e596305c e7931104 e3510000 0a000020
05-26 18:51:08.207: INFO/DEBUG(2894): stack:
05-26 18:51:08.207: INFO/DEBUG(2894): beb28cc8 00000001
05-26 18:51:08.207: INFO/DEBUG(2894): beb28ccc 4342cbe0
05-26 18:51:08.207: INFO/DEBUG(2894): beb28cd0 000001e4
05-26 18:51:08.207: INFO/DEBUG(2894): beb28cd4 00000004
05-26 18:51:08.207: INFO/DEBUG(2894): beb28cd8 42263150
05-26 18:51:08.207: INFO/DEBUG(2894): beb28cdc 4342cbdb
05-26 18:51:08.207: INFO/DEBUG(2894): beb28ce0 44707fd0
05-26 18:51:08.207: INFO/DEBUG(2894): beb28ce4 8008eb86 /system/lib/libdvm.so
05-26 18:51:08.207: INFO/DEBUG(2894): beb28ce8 00000007
05-26 18:51:08.207: INFO/DEBUG(2894): beb28cec 002d7c02
05-26 18:51:08.207: INFO/DEBUG(2894): beb28cf0 00000007
05-26 18:51:08.207: INFO/DEBUG(2894): beb28cf4 8005e489 /system/lib/libdvm.so
05-26 18:51:08.207: INFO/DEBUG(2894): beb28cf8 42263150
05-26 18:51:08.207: INFO/DEBUG(2894): beb28cfc 00000004
05-26 18:51:08.207: INFO/DEBUG(2894): beb28d00 df002777
05-26 18:51:08.207: INFO/DEBUG(2894): beb28d04 e3a070ad
05-26 18:51:08.207: INFO/DEBUG(2894): #00 beb28d08 80089a63 /system/lib/libdvm.so
05-26 18:51:08.207: INFO/DEBUG(2894): beb28d0c fffffe84
05-26 18:51:08.207: INFO/DEBUG(2894): beb28d10 44707fe4
05-26 18:51:08.207: INFO/DEBUG(2894): beb28d14 4051a518
05-26 18:51:08.207: INFO/DEBUG(2894): beb28d18 40009228
05-26 18:51:08.207: INFO/DEBUG(2894): beb28d1c 4051a3f8
05-26 18:51:08.207: INFO/DEBUG(2894): beb28d20 800a5600
05-26 18:51:08.207: INFO/DEBUG(2894): beb28d24 fffffe84
05-26 18:51:08.207: INFO/DEBUG(2894): beb28d28 00000001
05-26 18:51:08.217: INFO/DEBUG(2894): beb28d2c 0000000c
05-26 18:51:08.217: INFO/DEBUG(2894): beb28d30 4051a400
05-26 18:51:08.217: INFO/DEBUG(2894): beb28d34 80036028 /system/lib/libdvm.so
05-26 18:51:08.217: INFO/DEBUG(2894): #01 beb28d38 00005113
05-26 18:51:08.217: INFO/DEBUG(2894): beb28d3c 40009228
05-26 18:51:08.217: INFO/DEBUG(2894): beb28d40 00511400
05-26 18:51:08.217: INFO/DEBUG(2894): beb28d44 00000000
05-26 18:51:08.217: INFO/DEBUG(2894): beb28d48 400092fc
05-26 18:51:08.217: INFO/DEBUG(2894): beb28d4c 80000000 /system/lib/libdvm.so
05-26 18:51:08.217: INFO/DEBUG(2894): beb28d50 400091e8
05-26 18:51:08.217: INFO/DEBUG(2894): beb28d54 800368d0 /system/lib/libdvm.so
推荐答案
信号11(SIGSEGV)是发送到处理的信号时,它使一个无效的存储器参考,或段故障。特别是随着NDK工作时 - 在Android中,它往往通过像一个web视图或插件尝试使用更多的内存比可用造成的,而是各种各样的事情可能会导致它。试图释放()内存已被释放,例如,或者只是一个悬摆指针。举几个例子:
Signal 11 (SIGSEGV) is the signal sent to a process when it makes an invalid memory reference, or segmentation fault. In Android, it's quite often caused by something like a WebView or plugin trying to use more memory than is available, but all sorts of things can potentially cause it -- especially when working with the NDK. Trying to free() memory that has already been released, for example, or just a dangling pointer. A few examples:
<一个href="http://groups.google.com/group/android-ndk/browse_thread/thread/8d083a0ccebe0faa?pli=1">http://groups.google.com/group/android-ndk/browse_thread/thread/8d083a0ccebe0faa?pli=1
<一个href="http://stackoverflow.com/questions/6069866/catch-flash-out-of-memory-error-signal-11-in-webview">Catch在web视图闪了内存不足的错误?
不幸的是,具体的问题,不能从这里提供的信息来确定
Unfortunately, the specific problem cannot be determined from the information available here.
这篇关于什么可能导致Android的这个错误?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!