AbstractGoogleClient: Fatal signal 11 (SIGSEGV)

匿名 (未验证) 提交于 2019-12-03 01:48:02

问题:

06-06 00:05:02.955: I/DEBUG(5660): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 06-06 00:05:02.955: I/DEBUG(5660): Build fingerprint: 'google/occam/mako:4.2.2/JDQ39/573038:user/release-keys' 06-06 00:05:02.955: I/DEBUG(5660): Revision: '11' 06-06 00:05:02.955: I/DEBUG(5660): pid: 3787, tid: 3806, name: pool-1-thread-1  >>> com.example.android 

Symbolized:

RELADDR   FUNCTION                                                                                                            FILE:LINE 00022430  SSL_select_next_proto+26                                                                                            external/openssl/ssl/ssl_lib.c:1583 000223c3  next_proto_select_callback(ssl_st*, unsigned char**, unsigned char*, unsigned char const*, unsigned int, void*)+44  libcore/luni/src/main/native/org_apache_harmony_xnet_provider_jsse_NativeCrypto.cpp:3402 0002905f  ssl_parse_serverhello_tlsext+458                                                                                    external/openssl/ssl/t1_lib.c:1541 00015957  ssl3_get_server_hello+894                                                                                           external/openssl/ssl/s3_clnt.c:1103 00018193  ssl3_connect+618                                                                                                    external/openssl/ssl/s3_clnt.c:306 000235d7  SSL_connect+18                                                                                                      external/openssl/ssl/ssl_lib.c:948 v------>  ssl23_get_server_hello                                                                                              external/openssl/ssl/s23_clnt.c:783 0001126b  ssl23_connect+1970                                                                                                  external/openssl/ssl/s23_clnt.c:226 0002350f  SSL_do_handshake+66                                                                                                 external/openssl/ssl/ssl_lib.c:2577 00024c9d  NativeCrypto_SSL_do_handshake(_JNIEnv*, _jclass*, int, _jobject*, _jobject*, int, unsigned char, _jbyteArray*)+252  libcore/luni/src/main/native/org_apache_harmony_xnet_provider_jsse_NativeCrypto.cpp:3558 0001e290  dvmPlatformInvoke+112                                                                                               dalvik/vm/arch/arm/CallEABI.S:258 0004d411  dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)+396                                          dalvik/vm/Jni.cpp:1155 000276a0  dalvik_mterp+20                                                                                                     dalvik/vm/mterp/out/InterpAsm-armv7-a-neon.S:16240 0002b57c  dvmInterpret(Thread*, Method const*, JValue*)+184                                                                   dalvik/vm/interp/Interp.cpp:1956 0005fc31  dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)+272                                  dalvik/vm/interp/Stack.cpp:526 0005fc5b  dvmCallMethod(Thread*, Method const*, Object*, JValue*, ...)+20                                                     dalvik/vm/interp/Stack.cpp:429 000547d7  interpThreadStart(void*)+158                                                                                        dalvik/vm/Thread.cpp:1538 0000e3d8  __thread_entry+72                                                                                                   bionic/libc/bionic/pthread.c:204 0000dac4  pthread_create+160                                                                                                  bionic/libc/bionic/pthread.c:348

And than the app crashes. Google Drive API Client Library.

回答1:

I found the bug. After implementing the whole Google Drive Api by my own with the Apache HTTP client I also received those weired crash. As a result it wasn't the Google Drive API which was buggy.

I'm using the Picasso Library for fetching images in several adapters. Picasso uses the OkHttp Library to fetch those images. OkHttp seems to change something on the SSL context which causes all HTTPClients to behave pretty strange.

You can find a discussion and solution here: https://github.com/square/okhttp/issues/184



标签
易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!