Home > Mobile >  The NDK android7.0 models will appear under the crash log log are system library how to locate the p
The NDK android7.0 models will appear under the crash log log are system library how to locate the p

Time:11-12

Crash information is as follows:
11-09 15:37:14. 126 274 274 F the DEBUG: * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
11-09 15:37:14. 126 274 274 F the DEBUG: Build fingerprint: 'OnePlus/OnePlus2/OnePlus2: the 6.0.1/MMB29M/1447841200: user/release - keys'
11-09 15:37:14. 126 274 274 F the DEBUG: Revision: '0'
11-09 15:37:14. 126 274 274 F the DEBUG: ABI: 'x86'
11-09 15:37:14. 126 274 274 F the DEBUG: pid: 1426, dar: 1475, name: Thread - 98
11-09 15:37:14. 126 274 274 F the DEBUG: 11 (SIGSEGV) signal, code 1 (SEGV_MAPERR), fault addr 0 x9c
11-09 15:37:14. 134 274 274 F the DEBUG: Abort message: 'art/runtime/thread. Cc: 1237] Native thread exited without calling DetachCurrentThread: thread [24, tid=1475, Native, thread *=0 xae3f4a00, peer=0 x1366f0a0, "thread - 98]"'
11-09 15:37:14. 9, 134, 274, 274 F the DEBUG: eax d57f499 ebx b3abc94c ecx 9 d57f4a3 edx 9 d57f499
11-09 15:37:14. 9, 134, 274, 274 F the DEBUG: esi d57f478 edi 00000000
11-09 15:37:14. 134 274 274 F the DEBUG: XCS xes 00000073 XDS 0000007 b, 0000007 b XFS 0000003 b XSS 0000007 b
11-09 15:37:14. 134 274 274 F the DEBUG: eip b38bd653 ebp 00000000 esp 9 d57f3d0 flags 00210246
11-09 15:37:14. 139 274 274 F the DEBUG:
11-09 15:37:14. 139 274 274 F the DEBUG: backtrace:
11-09 15:37:14. 139 274 274 F the DEBUG: # 00 00547653 PC/system/lib/libart. So (_ZN3art14DumpCheckpoint3RunEPNS_6ThreadE + 435)
11-09 15:37:14. 139 274 274 F the DEBUG: # 01 0054 a3fe PC/system/lib/libart. So (_ZN3art10ThreadList13RunCheckpointEPNS_7ClosureE + 302)
11-09 15:37:14. 139 274 274 F the DEBUG: # 02 PC 0054 b6e3/system/lib/libart. So (_ZN3art10ThreadList4DumpERNSt3__113basic_ostreamIcNS1_11char_traitsIcEEEE + 243)
11-09 15:37:14. 139 274 274 F the DEBUG: # 3 PCS 005028 ca/system/lib/libart. So (_ZN3art7Runtime5AbortEv + 772)
11-09 15:37:14. 139 274 274 F the DEBUG: # 4 PCS 0014 b2b7/system/lib/libart. So (_ZN3art10LogMessageD2Ev + 1341)
11-09 15:37:14. 140 274 274 F the DEBUG: # 5 PCS 005331 f0/system/lib/libart. So (_ZN3art6Thread18ThreadExitCallbackEPv + 274)
11-09 15:37:14. 140 274 274 F the DEBUG: # 6 PC 00081 f37/system/lib/libc. So (_Z21pthread_key_clean_allv + 131)
11-09 15:37:14. 140 274 274 F the DEBUG: # 7 PC 00081 aa9/system/lib/libc. So pthread_exit (+ 71)
11-09 15:37:14. 140 274 274 F the DEBUG: # 000813 b9 08 PC/system/lib/libc. So (_ZL15__pthread_startPv + 64)
11-09 15:37:14. 140 274 274 F the DEBUG: # 09 PC 0002183 e/system/lib/libc. So (__start_thread + 25)
11-09 15:37:14. 141 274 274 F the DEBUG: # 10 PC 00016 f06/system/lib/libc. So (__bionic_clone + 70)
11-09 15:37:14. 350 274 274 F the DEBUG:
11-09 15:37:14. 350 274 274 F the DEBUG: Tombstone, written to:/data/tombstones tombstone_08
11-09 15:37:14. 350 274 274 E the DEBUG: AM write failed: Broken pipe
11-09 15:37:14. 358 532 579 I BootReceiver: Copying/data/tombstones tombstone_08 to DropBox (SYSTEM_TOMBSTONE)

CodePudding user response:

Native thread exited without calling DetachCurrentThread error reason
Take a look at this https://github.com/meganz/sdk/issues/81

CodePudding user response:

Intercept log, save to a local, next time to open the application to the background

CodePudding user response:

Bosses how specific operation have a link?

CodePudding user response:

refer to the second floor beginners - Study reply:
interception log, save to a local, next time to open the application to the background
bosses how specific operation have a link?
  • Related