Recently engaged in the analysis of iOS crash log, summed up:
The iphone development is going to be a non-stop version, followed by various versions of the crash log. If not properly managed, developers will soon be lost in the crash log and version of the ocean. As a background platform for the development of the moment for the sake of the client, the heart of the drunk.
The Mac has a free gadget--dwarfdump that can easily detect the app and the corresponding dsym.
It's easy to use. Three steps can be divided.
1> based on the crash log, the app's UUID is obtained. The UUID is a string consisting of 32 characters. With the UUID, you will know which version of you is having problems with the user's iphone.
2> uses Dwarfdump to check the app to see which app is the UUID above. command-line format:
Dwarfdump--uuid Yourapp.app/yourapp
3> use Dwarfdump to check whether the dSYM file is the above UUID. command-line format:
Dwarfdump--uuid YourApp.app.dSYM
If all three of the UUID are consistent, then congratulations, the crash log can be parsed correctly and stack traces information can be correctly obtained.