• 查看dsym错误信息


    To properly get symbols from your archived app's dSYM file and get useful information from your BugSense crash reports (or any other crash reports for that matter):

    1. Copy the stack trace from BugSense into TextEdit or any other text editor. Make sure to use the "clipboard" icon, rather than simply copying the text. Otherwise you will not get the actual memory locations of the stack trace, which are necessary to look up the references using atos and symbolicate your stack trace.
    2. Open XCode and go to the Organizer
    3. Find your archive and right-click it, go to open it in the finder.
    4. Navigate to the directory of the archive, usually ~/Library/Developer/XCode/Archives/YYYY-MM-DD/
    5. Go into the specific archive, and then the dSYMs folder
    6. You will see the file MyApp.app.dSYM and you may think, this is the file that I should run atosagainst! This is incorrect. It is actually another package! cd into this package, into the folder:MyApp.app.dSYM/Contents/Resources/DWARF and you will find another file simply called MyApp. This is the actual dSYM file.
    7. Run atos -arch armv7 -o MyApp 0x0000000 (or whatever the memory address is) to find the location of your error, or simply atos -arch armv7 -o MyApp to enter interactive mode.

    参考:http://stackoverflow.com/questions/7675863/atos-cannot-get-symbols-from-dsym-of-archived-application

  • 相关阅读:
    九,WPF资源
    八,WPF 命令
    七,WPF的元素绑定
    六,WPF的Application类
    五,控件
    四,路由事件
    三,依赖项属性
    二,WPF的布局
    一,XAML基础
    压缩解压缩字符串
  • 原文地址:https://www.cnblogs.com/vagrantatbeijing/p/3384735.html
Copyright © 2020-2023  润新知