Xcode's Crash log analysis

The general steps to resolve the bug from the crash file are in three steps:

A, get the crash log on the device.

b, analyze the crash log, locate the error location (navigate to the function and the number of lines of code).

C, open the code, change the bug.

1. Get the device log

1. When you can get to the phone that is running the app, or if the user is working with the export log. You can connect your device to your computer and then sync with itunes on your computer, and the crash log will sync to the folder you specified on your computer. (The above blog is indicated)

2. When you can get directly to the mobile phone running the app. You can connect your device to your computer, then open the Xcode software, select Window->devices, and you can view all the crash logs on your device in Xcode.

3. When the app is online, you can get the user's crash log via itunes Connect.

2, parsing logs

3, change the bug

References (stamp here):

> Leveraging logging tools in iOS development

> Xcode Crash Log analysis tool Symbolicatecrash usage

> Don't use Symbolicatecrash to parse crash log.

> Crash log analysis of iOS debugging

> Crash Log Analysis Basics for iOS apps

> Analyzing iOS Crash files: 3 ways to symbolize iOS crash files

> IOS App crash log analysis finishing

> Parsing of IOS crash files (i)

> iOS Crash-collecting iOS Crash-parsing iOS Crash-analysis

> Ramble on iOS Crash collection framework

> http://dev.umeng.com/analytics/reports/errors

Xcode's Crash log analysis