Use the dwarfdump command and the dsym file to link binary image to view the crash log...

Use the dwarfdump command and the dsym file to link binary image to view the crash log... first, you need to package the dsym file, and then enter the command in the terminal: 1 $ dwarfdump -- lookup = ADDRESS -- arch = ARCH {MyApp. app. dsym} 001NAME002 dwarfdump -- dump DWARF debug information.003 004SYNOPSIS005 dwarfdump [options] file1 file2... 006 007DESCRIPTION008 For each operand that names a mach-o or 32 bit ELF file, dwarfdump009 disassembles the DWARF data found within the file. only. debug _ Info010 section is disassembled unless one of the -- debug-XXXX or -- all options011 are specified1_12 013 The following options are available: 014 015-, -- all016 Dump disassembly of all DWARF sections -- by default only the017. debug_info section is disassembled, or individual sections can be018 specified by using the -- debug-XXXX options.019 020 -- arch = ARCH021 Dump DWARF debug information for Specified CPU ubunture000022 ubuntures may be specified by name or by number. this option023 can be specified multiple times, once for each desired024 architecture. all ubuntures will be disassembled by default.025 026-c, -- show-children027 Show a DIE's children when using the -- debug-info = OFFSET, -- find, 028 and -- name options.029 030 -- eh-frame [= SECTION] 031 Dump exception handling fra Me information from the optional SECTION032 parameter. the _ eh_frame section will be dumped by default.033 034-e, -- english035 Print dwarf tags and attributes in a more readable format instead036 of using the dwarf tag _ and AT _ definitions.037 038 -- file-stats [= size] 039 Show file composition statistics for any input files. each file 's040 contents are analyzed and broken down into byte counts The041 following categories: symbol table, string table, text and code, 042 DWARF debug information, STABS debug information, and other. when043 multiple files are specified, byte count totals for each category044 will be displayed at the end of the table. specify the optional045 'SIZE' argument to show all byte count results using unit suffixes: 046 Byte, Kilobyte, Megabyte, Gigabyte, Terabyte and Petabyte. this047 option can be useful in tracking the size and makeup of mach-o048 binary files, and also allows easy comparison between DWARF and049 STABS built binaries and related object files.050 051-f PATTERN, -- find = PATTERN052 Search for the exact text PATTERN in. debug_pubnames section053 and print the matching debug information entries. use the -- regex054 option to have PATTERN beco Me a regular expression for more055 flexible pattern matching31656 057 When there is no. debug_pubnames section or the name of the DIE you058 are looking for is not found in. debug_pubnames section, try059 using the slower but more complete -- name option000060 061-F, -- show-form062 Show DWARF form types after the DWARF attribute types000063 064-h ,-?, -- Help065 Show help and usage for this command.066 067-I, -- ignore-case068 Ignore case distinctions in when finding by name using strings or069 regular expressions.070 071-n PATTERN, -- name = PATTERN072 Find and print all DIE entries whose name (DW_AT_name attribute) 073 matches the exact text in PATTERN. use the -- regex option to074 have PATTERN become a regular expression for more flexible pattern075 matching31676 077 -- lookup = ADDRESS078 Lookup ADDRESS in the debug information and print out any available079 file, function, block and line table details.080 081-o PATH, -- out-file = PATH082 Redirect output to a file specified by PATH.083 084-p, -- show-parents085 Show a DIE's parents when using the -- debug-info = OFFSET, -- find, 086 and -- name options.087 088-r N, -- recurse-depth = N089 Only recurse to a child depth of N when displaying the DWARF090 information%91 092-u, -- uuid093 Show the UUID for each ubunture%94 095-x, -- regex096 Treat any PATTERN strings as regular expressions when searching097 instead of just as an exact string match000098 099-v, -- verbose100 Display verbose information when dumping. this can help to debug101 DWARF issues.102 103 -- verify104 Verify the structure of the DWARF information by verifying the105 compile unit chains, die relationships graph, and address ranges.106 107 -- version108 Display the current version and build date of the dwarfdump binary.109 110 -- debug-abbrev111 -- debug-aranges112 -- debug-frame [= OFFSET] 113 -- debug-info [= OFFSET] 114 -- debug-inlined115 -- debug-line [= OFFSET] 116 -- debug-macinfo [= OFFSET] 117 -- debug-pubnames [= PATTERN] 118 -- debug-pubtypes [= PATTERN] 119 -- debug-str120 -- apple-names [= PATTERN] 121 -- apple-types [= PATTERN] 122 -- apple-namespaces [= PATTERN] 123 -- apple-objc [= PATTERN] 124 Dump the specified DWARF section by name. only. debug_info125 section is disassembled by default. some entries support adding a126 '= OFFSET' as a way to provide an optional offset of the exact entry127 to dump within the respective section. when an OFFSET is provided, 128 only the entry at that offset will be dumped, else the entire129 section will be dumped. some options support an optional '= PATTERN' 130 parameter that will search the section for an entry with a matching131 name. children of items at OFFSETs can be dumped by also using the132 -- show-children option where applicable. the preceding describes how to use the dwarfdump command.