Application received signal SIGABRT
(null)
((
0 CoreFoundation 0x0000000182bbadc8 <redacted> + 148
1 libobjc.A.dylib 0x000000018221ff80 objc_exception_throw + 56
2 CoreFoundation 0x0000000182bbacf8 <redacted> + 0
3 Lazy 0x10034060c Lazy + 3409420 4 libsystem_platform.dylib 0x000000018281993c _sigtramp + 52 5 libsystem_pthread.dylib 0x0000000182820ef8 pthread_kill + 112 6 libsystem_c.dylib 0x00000001826c5dc8 abort + 140 7 libsystem_c.dylib 0x000000018269ae7c basename + 0 8 CoreGraphics 0x000000018411b0c8 <redacted> + 3444 9 CoreGraphics 0x00000001840283c4 <redacted> + 152 10 CoreGraphics 0x000000018402a470 <redacted> + 332 11 CoreGraphics 0x00000001840328e4 CGContextFillRects + 104 12 CoreGraphics 0x0000000184032974 CGContextFillRect + 52 13 Lazy 0x10014f98c Lazy + 1374604 14 Lazy 0x10014f058 Lazy + 1372248 15 Lazy 0x100257eb0 Lazy + 2457264 16 Lazy 0x100254f28 Lazy + 2445096 17 UIKit 0x0000000188045568 <redacted> + 76 18 UIKit 0x0000000187d3b0b4 <redacted> + 460 19 UIKit 0x0000000187df9a00 <redacted> + 300 20 UIKit 0x0000000187ed5d30 <redacted> + 1844 21 UIKit 0x00000001882adf30 <redacted> + 164 22 UIKit 0x0000000187ec2728 <redacted> + 172 23 UIKit 0x0000000187d4f7a0 <redacted> + 784 24 UIKit 0x00000001882af530 <redacted> + 72 25 UIKit 0x0000000187d0e4d8 <redacted> + 372 26 UIKit 0x0000000187d0b254 <redacted> + 2404 27 UIKit 0x0000000187d4d610 <redacted> + 1132 28 UIKit 0x0000000187d4cc0c <redacted> + 764 29 UIKit 0x0000000187d1d04c <redacted> + 248 30 UIKit 0x0000000187d1b628 <redacted> + 6568 31 CoreFoundation 0x0000000182b7109c <redacted> + 24 32 CoreFoundation 0x0000000182b70b30 <redacted> + 540 33 CoreFoundation 0x0000000182b6e830 <redacted> + 724 34 CoreFoundation 0x0000000182a98c50 CFRunLoopRunSpecific + 384 35 GraphicsServices 0x0000000184380088 GSEventRunModal + 180 36 UIKit 0x0000000187d86088 UIApplicationMain + 204 37 Lazy 0x10021cd9c Lazy + 2215324 38 libdyld.dylib 0x00000001826368b8 <redacted> + 4 ) dSYM UUID: 8822064E-9CEB-3B52-A2A3-9A35CAE53E06 CPU Type: arm64 Slide Address: 0x0000000100000000 Binary Image: Lazy Base Address: 0x00000001000c0000
這個問題通常是因爲程序訪問了不存在內存地址形成的崩潰app
解決步驟:ide
一、找到當時上傳代碼時使用的DYSM文件,這文件一般在.xcarchive文件中。 右鍵該文件, 而後經過終端工具跳轉到下面的DWARF文件夾中:工具
二、找到左邊列是你的app名字的幾列 看對應的右面內存地址並依次執行 。個人是arm64的cpu報錯,因此下面用arm64,若是其餘的是armv7或armv7s 相應的更改就能夠
$ atos -arch arm64 -o Lazy 0x10014f98coop
$ atos -arch arm64 -o Lazy 0x10014f058spa
$ atos -arch arm64 -o Lazy 0x100257eb0日誌
......orm
有幾個執行幾個,並依次記錄打印結果內存
就能夠看到這處內存地址反編譯回來的源碼行,能夠有效地幫助分析緣由。
注意,若是定位到的地址是UmengSignalHandler,要知道這個不是錯誤,是捕捉crash的方法,自己不引發crash, 當crash發生時由它來捕捉,直接忽略crash log中的 UmengSignalHandler 部分便可。ci
注:源碼
若是沒有打印出源碼行日誌,出現相似
atos cannot load symbols for the file Lazy for architecture armv7.
這樣的打印說明你的$ atos -arch arm64 -o Lazy 0x100257eb0 這個命令可能cpu類型不對或者內存地址不對