IOS-Comprehensive parsing. crash File crash report,

IOS-Comprehensive parsing. crash File crash report,
1. Preface I would like to think that every iOS siege lion will inevitably have access to the. crash file. What is the. crash file? All crash records of the iOS app are recorded on the device. Therefore, for iOS developers who do not integrate the crash report function with me, to obtain the crash file, you must first connect to the crashed machine and then export it from the crashed machine. crash file 2. how to resolve. the crash file is first exported. crash file, focus on the crash part of the record, such as clearly from this shard, we can not locate the specific error, and the specific number of lines of the crash. We get a binary report. At this time, we need to decompile it. Pair. we need to use three crash files for decompilation. 1. find. ipa file (the file that you package the app and upload it to the store) 2. 2. find. after the dSYM file Show in Finder. right-click the xcarchive file, and the package content is displayed. A folder named dSYMs is displayed. copy the dSYM file. 2. 3. set. ipa ,. crash ,. dSYMs files are stored in the same folder (for example, creating a bucket ash folder. 4. open your xcode and then open the code when you release it (remember to ensure that it is the code when you release it. If not, the number of lines pointing to the crash may be incorrect, or issues that cannot be resolved) 3. use xcode's built-in re-symbolicate to parse the crash report, click Devices, and then click View Device Logs to go in. Now open the bucket ash folder, and click. crash file drag In the right-hand box, right-click the re-symbolicate log to parse it for about 1-10 seconds. Then, we can find that the previous binary number is changed to the specific number of rows and specific values we want to see. crash reason. 4. if the Re-symbolicate provided by xocde still cannot be parsed, you need to use symbolicatecrash to manually parse symbolicatecrash using command lines, its path in my Mac is as follows (replace Xcode6.1.app with your Xcode name)/Applications/Xcode6.1.app/Contents/SharedFrameworks/DTDeviceKitBase. framework/Versions/A/Resources/symbolicatecrash copy the path and paste it under "go to folder" of the Finder to see the symbolicatecrash tool, now copy it to the desktop c Rash folder. Now, there are four files in the crash Folder:. app,. crash,. dSYM, and symbolicatecrash. Next, run the terminal to generate a crash that is easier to analyze.

./symbolicatecrash /Users/xxxx/Desktop/bugcrash/InOrder.crash /Users/xxxx/Desktop/bugcrash/InOrder.app.dSYM > Control_symbol.crash

In the preceding command, replace "xxxx" and "InOrder" with the corresponding name. Run. at this time, the terminal may report Error: "cmd_dir" is not defined at/usr/local/bin/symbolicatecrash line 53. at this time, enter the following in the terminal (Xcode6.1.app is still to be replaced with the actual name) and then run the command, now let's take a look at the crash folder on the desktop. There will be an extra file named "Control_symbol.crash". Let's open it and take a look. Same as just now. If you have any questions, please leave a message below. If you have time, I will reply one by one. Thank you. Author: Clear Saup
Source: http://www.cnblogs.com/qingche/
The copyright of this article is shared by the author and the blog. You are welcome to repost it, but you must keep this statement and provide a connection to the original article on the article page.