1. PrefaceEvery iOS siege lion wants to come into contact with. crash fileso what is the. crash file?All crash records for iOS apps are recorded on the device, so for iOS developers who have no integration with me to send crash reports, the crash file must be connected to a crashed machine and then exported from the crashed machine. Crash file2. How to resolve. Crash FilesLet's take a look at the lead-in. crash file, focusing on the crash section of the record as clearly from this diagram, we can not pinpoint the specific error, and the exact number of crashes. We have a binary report, and we need to decompile it. Decompile A. Crash file we need to use three files, which is indispensable2.1. Find the. IPA file when you publish your app (that is, the file you uploaded to the store for your packaged app)2.2. The. dsym file that was generated when archive was foundThe show in Finder right-click on this. xcarchive file in the folder to display the contents of the package, you can see a folder named Dsyms, the inside of the. dsym file copied out2.3. Place the.IPA,. Crash,. dsyms files in the same folder (for example, create a Bugcrash folder)2.4. Open your Xcode and open the code when you publish (remember that you must ensure that you publish the code, if not, there may be points to the number of crashes or unresolved problems)3. Use Xcode to bring re-symbolicate to resolve crash reportsClick Devices to go in and click View Device Logs go inside now openBugcrash folder, then drag the. crash file into the right box and select the right button re-Symbolicate Logto parseafter about 1-10 seconds, we can see that the previous binary number has become the exact number of lines we want to see and the specific. Crash reason.4. If Xocde's own re-symbolicate is still unresolved, then we need to use Symbolicatecrash to manually parse it with the command lineSymbolicatecrash is a hidden tool that has the exact path in my Mac as follows (Xcode6.1.app please change to your Xcode name)/applications/xcode6.1.app/contents/ Sharedframeworks/dtdevicekitbase.framework/versions/a/resources/symbolicatecrash copy this path and glue it to the finder's "Go to Folder", Go, you can see the Symbolicatecrash tool, and now it is also copied to the Desktop Crash folder. At this point, the crash folder now has 4 files, respectively. App,. Crash,. DSYM, Symbolicatecrash. The next step is to use the terminal to knock commands to generate crash that are easier to analyze.
./symbolicatecrash/users/xxxx/desktop/bugcrash/inorder.crash/users/xxxx/desktop/bugcrash/inorder.app.dsym > Control_symbol.crash
In the above command, "xxxx" and "inorder" should be replaced by their respective names. Run, this time the terminal may error Error: "Developer_dir" is not defined At/usr/local/bin/symbolicatecrash line 53. This time in the terminal and then enter the following (Xcode6.1.app is still to replace the actual name) and then run the first command, then look at the Desktop Crash folder will be more than a file called "Control_symbol.crash", we open to see. And just the same. If there is nothing to understand welcome in the following message, I have time to reply, thank you.Clear Saup
Source: http://www.cnblogs.com/qingche/
This article is copyright to the author and the blog Park is shared, welcome reprint, but must retain this paragraph statement, and in the article page obvious location to give the original text connection.
ios-All-round parsing. Crash file crash report
