Using an App Review .crash file

Hello Folks;

I'm trying to utilize a crash log from App Review. I've uploaded the app with DWARF with dSYM File. When I open the App Review .crash file in Xcode I see this:

#0	in __pthread_kill ()
#1	in pthread_kill ()
#2	in abort ()
#3	in abort_message ()
#4	in demangling_terminate_handler() ()
#5	in _objc_terminate() ()
#6	in std::__terminate(void (*)()) ()
#7	in std::terminate() ()
#8	in _dispatch_client_callout ()
#9	in _dispatch_main_queue_callback_4CF ()
#10	in __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ ()
#11	in __CFRunLoopRun ()
#12	in CFRunLoopRunSpecific ()
#13	in RunCurrentEventLoopInMode ()
#14	in ReceiveNextEventCommon ()
#15	in _BlockUntilNextEventMatchingListInModeWithFilter ()
#16	in _DPSNextEvent ()
#17	in -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] ()
#18	in -[NSApplication run] ()
#19	in NSApplicationMain ()
#20	in 0x10a062000 ()
#21	in 0x10a062000 ()
#22	in start ()

Whereas in Console it looks like this:

0   CoreFoundation                      0x00007fff2053783b __exceptionPreprocess + 242
1   libobjc.A.dylib                     0x00007fff2026fd92 objc_exception_throw + 48
2   CoreFoundation                      0x00007fff205609a2 +[NSException raise:format:arguments:] + 88
3   Foundation                          0x00007fff2131e4d2 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 191
4   AppKit                              0x00007fff22d02679 -[NSCell _objectValue:forString:errorDescription:] + 260
5   AppKit                              0x00007fff22d024d3 -[NSCell setStringValue:] + 44
6   AppKit                              0x00007fff22d7af3e -[NSControl setStringValue:] + 121
7   AppXYZ                               0x000000010a069107 AppXYZ + 28935
8   AppXYZ                               0x000000010a07eed1 AppXYZ + 118481
9   libdispatch.dylib                   0x00007fff20219623 _dispatch_call_block_and_release + 12
10  libdispatch.dylib                   0x00007fff2021a806 _dispatch_client_callout + 8
11  libdispatch.dylib                   0x00007fff20226b4f _dispatch_main_queue_callback_4CF + 940
12  CoreFoundation                      0x00007fff204fa5a8 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9
13  CoreFoundation                      0x00007fff204bc7a2 __CFRunLoopRun + 2755
14  CoreFoundation                      0x00007fff204bb61c CFRunLoopRunSpecific + 563
15  HIToolbox                           0x00007fff28701a83 RunCurrentEventLoopInMode + 292
16  HIToolbox                           0x00007fff287017e5 ReceiveNextEventCommon + 587
17  HIToolbox                           0x00007fff28701583 _BlockUntilNextEventMatchingListInModeWithFilter + 70
18  AppKit                              0x00007fff22cc3172 _DPSNextEvent + 864
19  AppKit                              0x00007fff22cc1945 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1364
20  AppKit                              0x00007fff22cb3c69 -[NSApplication run] + 586
21  AppKit                              0x00007fff22c87e6c NSApplicationMain + 816
22  AppXYZ                               0x000000010a155a62 AppXYZ + 997986
23  AppXYZ                               0x000000010a155afb AppXYZ + 998139
24  libdyld.dylib                       0x00007fff203dff3d start + 1
25  ???                                 0x0000000000000001 0x0 + 1

So what am trying to understand is how to utilize lines 7 & 8 in the Console.

Reading through the Docs (https://developer.apple.com/documentation/xcode/adding-identifiable-symbol-names-to-a-crash-report#Symbolicate-the-Crash-Report-in-Xcode) it seems like I should use 'atos' but its not working out....

For starters there is no 'Binary Architecture' information in the 'Binary Images' section of the .crash file.

Can someone point out what I need to do here or clarify my misunderstanding?

Thank for any help! Steve

Answered by SwampDog in 687428022

For the record, I am answering my own question.

Yes, 'atos' was the correct tool to use. The key was realizing that the '.archive' file was needed by 'atos'...

In addition to the console text shown above, there was also this snippet:

...
Binary Images:
       0x10a062000 - 0x10a325fff +[devProdID] (2.2.3 - 3302) <9248A949-D5CB-3C44-924B-2A9403061E7B> /Applications/AppXYZ.app/Contents/MacOS/AppXYZ
...

So the actual command which achieved the desired result was:

atos -arch x86_64 -o /Users/steve/Library/Developer/Xcode/Archives/2021-09-10/AppXYZ\ 9-10-21,\ 9.05\ PM.xcarchive/dSYMs/AppXYZ.app.dSYM/Contents/Resources/DWARF/AppXYZ -l 0x10a062000 0x000000010a069107
Accepted Answer

For the record, I am answering my own question.

Yes, 'atos' was the correct tool to use. The key was realizing that the '.archive' file was needed by 'atos'...

In addition to the console text shown above, there was also this snippet:

...
Binary Images:
       0x10a062000 - 0x10a325fff +[devProdID] (2.2.3 - 3302) <9248A949-D5CB-3C44-924B-2A9403061E7B> /Applications/AppXYZ.app/Contents/MacOS/AppXYZ
...

So the actual command which achieved the desired result was:

atos -arch x86_64 -o /Users/steve/Library/Developer/Xcode/Archives/2021-09-10/AppXYZ\ 9-10-21,\ 9.05\ PM.xcarchive/dSYMs/AppXYZ.app.dSYM/Contents/Resources/DWARF/AppXYZ -l 0x10a062000 0x000000010a069107
Using an App Review .crash file
 
 
Q