Android 如何找出我的应用程序支持哪些平台架构?

Android 如何找出我的应用程序支持哪些平台架构?,android,android-build,Android,Android Build,我在play store开发者控制台中收到一些崩溃报告,所有这些崩溃都发生在armeabi-v7a平台设备上。以下是坠机报告: Build fingerprint: 'samsung/m0xx/m0:4.3/JSS15J/I9300XWUGML4:user/release-keys' Revision: '12' pid: 19738, tid: 19738, name: something.android >>> com.something.android <<

我在play store开发者控制台中收到一些崩溃报告,所有这些崩溃都发生在
armeabi-v7a
平台设备上。以下是坠机报告:

Build fingerprint: 'samsung/m0xx/m0:4.3/JSS15J/I9300XWUGML4:user/release-keys'
Revision: '12'
pid: 19738, tid: 19738, name: something.android  >>> com.something.android <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadd00d
    r0 00000000  r1 00000000  r2 00000000  r3 40baf1a0
    r4 deadd00d  r5 0000020c  r6 42a2de60  r7 40b44c51
    r8 401091f4  r9 58220c40  sl 41ea7a70  fp befad3ec
    ip 4d1a4001  sp befad0e8  lr 00000001  pc 40b3f33c  cpsr 60000030
    d0  000000000000000f  d1  4000000000000000
    d2  ffffffffffffffff  d3  ffffffffffffffff
    d4  8000000000000000  d5  3fcef049fb9094d1
    d6  3f00000000000000  d7  3f8000003f800000
    d8  0000000000000000  d9  0000000000000000
    d10 0000000000000000  d11 0000000000000000
    d12 0000000000000000  d13 0000000000000000
    d14 0000000000000000  d15 0000000000000000
    d16 000000000000000e  d17 0400050101010df7
    d18 4146605000000000  d19 0065004e005f0061
    d20 3f8948b0fcd6e9e0  d21 3fe555b0aaeac752
    d22 3fd24998d6307188  d23 3fcc7288e957b53b
    d24 3fc74721cad6b0ed  d25 3fc2f112df3e5244
    d26 40026bb1bbb55516  d27 4000000000000000
    d28 40008df2d49d41f1  d29 3fb0f4a31edab38b
    d30 3ff0000000000000  d31 3f4de16b9c24a98f
    scr 60000010

backtrace:
    #00  pc 0004633c  /system/lib/libdvm.so (dvmAbort+67)
    #01  pc 0004ad8f  /system/lib/libdvm.so (dvmDecodeIndirectRef(Thread*, _jobject*)+146)
    #02  pc 0004bc6d  /system/lib/libdvm.so
    #03  pc 0029b609  /system/lib/libwebcore.so
    #04  pc 0028f899  /system/lib/libwebcore.so
    #05  pc 0028f973  /system/lib/libwebcore.so
    #06  pc 00295c99  /system/lib/libwebcore.so
    #07  pc 0001e48c  /system/lib/libdvm.so (dvmPlatformInvoke+112)
    #08  pc 0004e95b  /system/lib/libdvm.so (dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)+398)
    #09  pc 000278a0  /system/lib/libdvm.so
    #10  pc 0002be40  /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+184)
    #11  pc 00060d6b  /system/lib/libdvm.so (dvmInvokeMethod(Object*, Method const*, ArrayObject*, ArrayObject*, ClassObject*, bool)+350)
    #12  pc 00068a2f  /system/lib/libdvm.so
    #13  pc 000278a0  /system/lib/libdvm.so
    #14  pc 0002be40  /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+184)
    #15  pc 00060aad  /system/lib/libdvm.so (dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)+292)
    #16  pc 0004a53b  /system/lib/libdvm.so
    #17  pc 00054aa3  /system/lib/libandroid_runtime.so
    #18  pc 00055fcb  /system/lib/libandroid_runtime.so (android::AndroidRuntime::start(char const*, char const*)+378)
    #19  pc 0000105b  /system/bin/app_process
    #20  pc 0000dc4f  /system/lib/libc.so (__libc_init+50)
    #21  pc 00000d7c  /system/bin/app_process

code around pc:
    40b3f31c f8d54a18 462034cc f44f447a f7d77100  
    40b3f32c 2200ebc4 5d114615 e004b9a9 4c0d4780  
    40b3f33c f7d77025 4910ecfe 4a102006 447a4479  
    40b3f34c eb7cf7d7 f7d72000 4b0dec34 6dd8447b  
    40b3f35c d1eb2800 3201e7eb f5b2186d d0ea7f00  
    40b3f36c bf00e7e1 deadd00d 0006b96e fffffe5c  
    40b3f37c 0006fe8a 0004fb0b 0004eeee 00050dae  
    40b3f38c 0006fe44 4604b570 68406806 f1a0e005  
    40b3f39c 46280518 fc9ef7f3 42b04628 6820d1f7  
    40b3f3ac 68a1b128 f0221a0a f7ff0107 4620fe6a  
    40b3f3bc 0000bd70 f00fb570 4b3dfd03 f8d3447b  
    40b3f3cc b10803cc f8d6f01e 25004c3a 6c20447c  
    40b3f3dc eb22f7d7 64256ea0 eb1ef7d7 66a56f20  
    40b3f3ec eb1af7d7 f00c6725 f00cf9e1 f8d4fc0f  
    40b3f3fc 28030098 f02dd101 f00ffef5 492efa47  
    40b3f40c f8914479 b1322033 2003492c 44794a2c  

code around lr:
    00000000 ffffffff ffffffff ffffffff ffffffff  
    00000010 ffffffff ffffffff ffffffff ffffffff  
    00000020 ffffffff ffffffff ffffffff ffffffff  
    00000030 ffffffff ffffffff ffffffff ffffffff  
    00000040 ffffffff ffffffff ffffffff ffffffff  
    00000050 ffffffff ffffffff ffffffff ffffffff  
    00000060 ffffffff ffffffff ffffffff ffffffff  
    00000070 ffffffff ffffffff ffffffff ffffffff  
    00000080 ffffffff ffffffff ffffffff ffffffff  
    00000090 ffffffff ffffffff ffffffff ffffffff  
    000000a0 ffffffff ffffffff ffffffff ffffffff  
    000000b0 ffffffff ffffffff ffffffff ffffffff  
    000000c0 ffffffff ffffffff ffffffff ffffffff  
    000000d0 ffffffff ffffffff ffffffff ffffffff  
    000000e0 ffffffff ffffffff ffffffff ffffffff  
    000000f0 ffffffff ffffffff ffffffff ffffffff
Build fingerprint:'samsung/m0xx/m0:4.3/JSS15J/I9300XWUGML4:user/release key'
修订:‘12’

pid:19738,tid:19738,name:something.android>>>com.something.android“所有这些崩溃都发生在armeabi-v7a平台设备上”--这是因为绝大多数Android设备运行的是
armeabi-v7a
CPU。@Commonware如何支持这些设备?为什么不先告诉我们崩溃的实际崩溃堆栈跟踪,你给出的不是stacktrace@tyczj应用程序一启动就会在这些设备上崩溃。所以我对Crashlytics一无所获。这是我从play store开发者控制台得到的唯一东西。“我如何支持这些设备?”——可能你已经做到了。除非您在大约80%的Android设备上崩溃,否则您的问题并不特定于CPU架构。