Today, in the Friend League error analysis, found a such error:
Application received signal SIGSEGV (NULL) (0 corefoundation 0x2ef6dfeb + 154 1 LIBOBJC. A.dylib 0X3971CCCF Objc_exception_throw + 2 corefoundation 0X2EF6DF15 + 0 3 appname 0xcc979 APPNAME + 821625 4 Libsyste M_platform.dylib 0x39d43f8b _sigtramp + 5 UIKit 0x31842261 + 6 UIKit 0x31842261 + 7 UIKit 0x31842261 + 8 UIKit 0X318AB1D9 + 9 UIKit 0x3182d97f + 142 UIKit 0X318AAEFD + 1 UIKit 0x31808115 + 312 UIKit 0x31808407 + 106 3 UIKit 0x31884c37 + 0x2f94d163 Foundation, __nsfiredelayedperform + 414, corefoundation 0x2ef391b7 + + Corefou Ndation 0X2EF38DCF + 782 corefoundation 0x2ef3716b + 1210-corefoundation 0x2eea1f0f cfrunlooprunspecific + 522 Co Refoundation 0X2EEA1CF3 Cfrunloopruninmode + 106 graphicsservices 0x33da6663 Gseventrunmodal + 138 UIKit 0x317ed16d Uiapplicationmain + 1136 Verywallen 0x85613 Verywallen + 529939 libdyld.dylib 0x39c29ab7 + 2) DSYM Uuid:76634c55-b 73f-303d-ba7c-511d5b84d45a CPU type:armv7 Slide Address: 0x00004000 Binary Image:verywallen Base address:0x0008b000
Application received signal SIGSEGV (NULL)
SIGSEGV and Sigbus are generally caused by accessing memory that has been freed or by calling a method that does not exist, then the above-mentioned crash information basically can be defined as memory is released? The problem is where it collapsed, completely don't know ah, so can only look inside.
Use Showinfinder to enter
/Users/username(电脑名)/Library/Developer/Xcode/Archives/这个文件夹,你会看到你打包时生成的
xcarchive
文件,当然你得用Archives来打包。
然后来查找正确的包吧,也就是崩溃程序的这个包的dSYM UUID必须和上面崩溃信息的一样。
打开终端,输入cd 然后拖进
xcarchive
File it, remember to add/dSYMs然后回车,这样你就进入了/dSYMs的目录了,再输入
命令,可别脑子坏掉的也输appname就成,然后你就能看到
armv7 和 armv7s的 两个UUID了,对比下就能知道是否是这个包了,不是就继续试直到找到位置
当你找到是哪个包了在来看下一步。。。
看看这句
This is where the crash is called when the terminal continues to enter
对应的包的路径/dSYMs/appname.app.dSYM/Contents/Resources/DWARF/appname
就会得出结果,如果你前面没有敲错,那么你应该能看到不一样的Log信息,不是么,
Take a look at the results: There are at_name, Line table dir:, lines table file, yes, you can find the wrong file, which row ...
So the rest is on your own judgment ...
Today!!!
Still don't understand this, I also follow the footsteps of the predecessors
http://lieyunye.github.io/blog/2013/09/10/how-to-analyse-ios-crash-log/
Go Error analysis of Umeng