Find the cause of the problem by crashing trace.

Here we take an example of the error message captured by Umeng:

From the Friends League, we may get the following information:

Application received signal SIGSEGV

(NULL) (0 corefoundation 0x359348a7 __exceptionpreprocess + 1861 LIBOBJC. A.dylib 0x37cdb259 Objc_exception_throw + 322 corefoundation 0x35934789 +[nsexc Eption Raise:format:] + corefoundation 0x359347ab +[nsexception Raise:format:] + 344 Nxxmovie0X1153B9 _mh_execute_header + 11314495 libsystem_c.dylib 0x32d407e3 _sigtramp + 386 Nxxmovie0X390FB _mh_execute_header + 2296277 corefoundation 0x358931fb-[nsobject performselector:withobjec T:] + 428 Nxxmovie0x175a5 _mh_execute_header + 915579 corefoundation 0x358931fb-[nsobject performselector:withobject:] + 4210 Foundation 0 x35457747 __nsthreadperformperform + 35011 corefoundation 0x35908ad3 __cfrunloop_is_calling_out_to_a_source0_perform _function__ + 1412 Corefoundation 0x3590829f __cfrunloopdosources0 + 21413 corefoundation 0x35907045 __CFRunLoopRun + 6521 4 corefoundation 0x3588a4a5 cfrunlooprunspecific + 30015 corefoundation 0x3588a36d Cfrunloopruninmode + 10416 GraphicsSer Vices 0x37526439 gseventrunmodal + 13617 UIKit 0x33396cd5 uiapplicationmain + 108018 Nxxmovie0x31b7 _mh_execute_header + 863119 nxxmovie 0x3150 _mh_execute_header + 8528) DSYM UUID: Ff67f6d3-c71c-3a7d-9c4c-c4ffbf8eeeb9cpu type:armv7slide address:0x00001000binary image:nxxmoviebase Address: 0x000f4000 

Because this type of crash information is often difficult to reproduce, there is no repro step, so we have to find the original code when the release is released, and may need to revert back to the previous SVN or Git version.

Then find the Dysm file that was used when uploading the code, which is usually in the. xcarchive file. Right-click the file and then through the Terminal tool CD to

Cd/users/heqin/downloads/xxxmovie2.0.0_apps_0605_2104\ 13-6-5\ pm 9.02.xcarchive/dsyms/xxxmovie.app.dsym/contents /resources/dwarf

Note: 1. For projects that successfully generate Archvie, in this archive package, it is possible to display the contents of the package, see the Dsyms folder and a Products folder, continue to display the Dsyms folder, Can see a Xxx.app.DSYM file, continue to display the contents of the package, you can see the contents/resources/dwarf/xxxx file, this file is compiled binary file, through which it can be decompile, to find the binary corresponding source location.

2. In Xcode, after successful archive, you can see all the archive files in the Organizer interface archives, right-click the show in Finder to find this file.

Then execute Atos-arch armv7-o xxxmovie 0x1153b9. You can see the source line that this memory address is back-compiled.

Can effectively help to analyze the cause.

Original address: http://blog.csdn.net/smking/article/details/9342899

Find the cause of the problem by crashing trace.