Analyze the app crash log of the Friends league stats

To parse the crash log, you first need to keep the compiled. xcarchive file at the time of publication. This file contains the. dSYM file.

Where is this file? Open the Xcode-> menu Window->organizer, and Right-click on the compiled file to open it.

Recommended visualization Tools:

This is the crash log that I've counted in my project, and if you look at those log reports, you won't know what line of code is causing it.

To use this method, drag the corresponding version of the. xcarchive file to the tool. Compare the UUID to the Friend Union log, and copy the wrong address information to the arrow. Click Analyze.

You can get the exact code crash location. It's simple. (Note: The file name does not appear in Chinese, otherwise selected file Flash)

DSYM File Analysis Tool http://answerhuang.duapp.com/index.php/2014/07/06/dsym_tool/

This is the blogger Answer-huang has developed a tool that is designed to quickly locate the crash log code.

Tools by Jongfangzhi comrade uploaded to Csdn download, is free of credit download.

Address: http://download.csdn.net/detail/totogo2010/8012367

Problems encountered:

Application received signal SIGSEGV (NULL) (0 corefoundation 0x2d948f9b <redacted> + 154 1 LIBOBJC. A.dylib 0X380CCCCF Objc_exception_throw + 2 corefoundation 0x2d948ec5 <r edacted> + 0 3 appName 0x10ca11 appName + 1083921 4 libsystem_platform.dylib 0x                               386F3F8B _sigtramp + 5 UIKit 0x305ffa87 <redacted> + 6 UIKit 0x3037cad7 <redacted> + 94 7 UIKit 0x3037c891 <redacted> + 5 8 UIKit 0x3028403f <redacted> + 1078 9 UIKit 0x                               30336357 <redacted> + 214 UIKit 0x301e56d5 <redacted> + UIKit 0x3015e53b <redacted> + 430 corefoundation 0x2d914255 <redact
Ed> + 20	Corefoundation 0x2d911bf9 <redacted> + 284 corefoundation 0x2d91 1F3B <redacted> + 730 corefoundation 0X2D87CEBF cfrunlooprunspecific + 522 Corefounda tion 0X2D87CCA3 Cfrunloopruninmode + 106 graphicsservices 0x32782663 gseventr                        Unmodal + 138 UIKit 0x301c914d Uiapplicationmain + 1136 AppName 0x232a7 appName + 127655 libdyld.dylib 0x385d9ab7 <redacted> + 2) DSYM UUID:FAB10 807-58f9-3e96-9eb2-2a93293d6141 CPU type:armv7 Slide address:0x00004000 Binary image:appname Base address:0x0002f000

Application received signal SIGSEGV: returned error after analysis with this software:

Umengsignalhandler (in AppName) + 137 (This egg hurts ...) ）

so I tried the second method:

1. Find the Dysm file used when submitting the app.
Find the version of the error from Xcode->window->organizer, find AppName.app.dSYM from its. xcarchive->dsyms, continue to enter, contents- >resources->dwarf, finally found appName . This is the compiled binary file.

2. Atos-o appName. app.dsym/contents/resources/dwarf/appName 0x00062867 (Note: file path) can also be AppName copy out, in the appName corresponding directory executes the following code, be aware of Binary Image and CPU Type atos-arch armv7-o C12>appname0x00062867

However, it did not solve my problem: still return

Umengsignalhandler (in appName) + 137 (at this time of my mood, you can understand it)

Not yet , I tried the third method:

1. Enter the dSYM file

2. Check to see if the app UUID matches the UUID in the friend log.

3. Match the corresponding memory address to the correct location.

Cd/users/username/library/developer/xcode/archives/2013-08-30/app 8-30-13 6.19 pm.xcarchive/dsyms
dwarfdump-- UUID Appname.app.dSYM
uuid:9f0aefa6-4349-30af-8420-bcee739da0b4 (armv7) appname.app.dsym/contents/resources/ Dwarf/appname
uuid:365ef56e-d598-3b94-ad36-bfa13772a4e3 (armv7s) appname.app.dsym/contents/resources/dwarf/ AppName

If the dsym uuid in the crash log matches the local Dysm file

Dwarfdump--arch=armv7--lookup 0x97525  /users/username/library/developer/xcode/archives/2013-08-30/appname\ 8-30-13\ 6.19\ Pm.xcarchive/dsyms/appname.app.dsym/contents/resources/dwarf/appname

The results are as follows:

----------------------------------------------------------------------
 File:/users/lmj/desktop/1.8.2. Xcarchive/dsyms/appname.app.dsym/contents/resources/dwarf/appname (ARMV7)
--------------------------------- -------------------------------------
looking up address:0x000000000010ca11 in. Debug_info ... not found.
Looking up address:0x000000000010ca11 in. Debug_frame ... not found.

(I'm drunk, too.) (who solved this, welcome message)

This article thanks Bo master Jongfang Zhi