UMeng"Application received signal SIGSEGV"错误分析
2015-03-03 17:54
471 查看
从友盟中, 我们可能会得到如下信息:
找到当时上传代码时使用的DYSM文件,这文件通常在.xcarchive文件中。 右键该文件, 然后通过Terminal工具跳转到下面的DWARF文件夹中:
然后执行
就可以看到这处内存地址反编译回来的源码行,可以有效地帮助分析原因。
注意,如果定位到的地址是UmengSignalHandler,要知道这个不是错误,是捕捉crash的方法,本身不引起crash, 当crash发生时由它来捕捉,直接忽略crash log中的 UmengSignalHandler 部分即可。
参考文章:
通过崩溃trace来查找问题原因
Application received signal SIGSEGV (null) ( 0 CoreFoundation 0x00000001866fde64 <redacted> + 160 1 libobjc.A.dylib 0x0000000196df80e4 objc_exception_throw + 60 2 CoreFoundation 0x00000001866fdd88 <redacted> + 0 3 xxxDance 0x1005b9d94 _ZN15CTXAppidConvert17IsConnectionAppIdEPKc + 587496 4 libsystem_platform.dylib 0x000000019761494c _sigtramp + 52 5 ??? 0x0000000000000014 0x0 + 20 6 GLEngine 0x000000018a1e12c4 <redacted> + 144 7 GLEngine 0x000000018a187f54 <redacted> + 988 8 xxxDance 0x1003f5120 _ZN9_baidu_vi7CVArrayIjjE6AppendERKS1_ + 7920 9 xxxDance 0x1003f39a4 _ZN9_baidu_vi7CVArrayIjjE6AppendERKS1_ + 1908 10 xxxDance 0x10045c564 _ZN9_baidu_vi7CVArrayINS_12CVHttpClient16tag_PostDataInfoERS2_ED2Ev + 30940 11 xxxDance 0x100406ebc _ZN9_baidu_vi7CVArrayIN16_baidu_framework17tagHttpClientItemERS2_ED2Ev + 44932 12 xxxDance 0x100409278 _ZN9_baidu_vi7CVArrayI19tag_PaoPaoAttributeRS1_ED2Ev + 3260 13 libdispatch.dylib 0x000000019743d3ac <redacted> + 24 14 libdispatch.dylib 0x000000019743d36c <redacted> + 16 15 libdispatch.dylib 0x0000000197441980 _dispatch_main_queue_callback_4CF + 932 16 CoreFoundation 0x00000001866b56a0 <redacted> + 12 17 CoreFoundation 0x00000001866b3748 <redacted> + 1492 18 CoreFoundation 0x00000001865e11f4 CFRunLoopRunSpecific + 396 19 GraphicsServices 0x000000018f7775a4 GSEventRunModal + 168 20 UIKit 0x000000018af12784 UIApplicationMain + 1488 21 xxxDance 0x100200b6c xxxDance + 2100076 22 libdyld.dylib 0x0000000197466a08 <redacted> + 4 ) dSYM UUID: AC5A1E49-1E38-3CD7-BD6F-DE49294F03AF CPU Type: arm64 Slide Address: 0x0000000100000000 Binary Image: xxxDance Base Address: 0x0000000100044000
找到当时上传代码时使用的DYSM文件,这文件通常在.xcarchive文件中。 右键该文件, 然后通过Terminal工具跳转到下面的DWARF文件夹中:
$ cd ~/Library/Developer/Xcode/Archives/yyyy-mm-dd/appname.xcarchive/dSYMs/appname.app.dSYM/Contents/Resources/DWARF
然后执行
$ atos -arch arm64 -o xxxMovie 0x1153b9
就可以看到这处内存地址反编译回来的源码行,可以有效地帮助分析原因。
注意,如果定位到的地址是UmengSignalHandler,要知道这个不是错误,是捕捉crash的方法,本身不引起crash, 当crash发生时由它来捕捉,直接忽略crash log中的 UmengSignalHandler 部分即可。
参考文章:
通过崩溃trace来查找问题原因
相关文章推荐
- 友盟 Application received signal SIGSEGV 解析错误日志
- 错误总结:C/C++运行时提示".exe已停止工作"? 调试时出现Program received signal SIGSEGV,Segmentation fault?引用无效内存一般是什么错误?
- Application received signal SIGSEGV通过崩溃trace来查找问题原因
- Application received signal SIGSEGV
- IOS开发:Program received signal: “EXC_BAD_ACCESS" 问题分析
- Application received signal SIGSEGV
- Thead 1:proogram received signal:"SIGABRT" 错误
- Application received signal SIGSEGV
- "Thread 1:Program received signal:"SIGABRT" "分析
- 添加地图的时候 program received signal: "EXC_ARITHMETIC 错误
- 通过崩溃trace来查找问题原因 Application received signal SIGSEGV(null)
- Thread 1:Program received signal:"SIGABRT"错误之一
- QApplication::~QApplication(void)" (__imp_??1QApplication@@UAE@XZ) referenced in function _main 错误(转)
- Program received signal SIGSEGV, Segmentation fault.
- 从kernel源代码的角度分析signal的错误用法和理解
- WebService开发时错误,Received content of invalid Content-Type setting:text/html - SOAP expects "text/xml"
- socket错误:Program received signal SIGPIPE, Broken pipe
- MySQL 实例配置的"Apply security settings"错误 、 Java通过JDBC无法连接MySQL的 分析
- 解析:Program received signal: “EXC_BAD_ACCESS"(
- thread 1:Program received signal: "SIGABRT" 什么原因?