Which way is the call stack in a crash log? I've got a crash log from 
com.apple.dock.extra that is:

Process:         com.apple.dock.extra [466]
Path:            
/System/Library/CoreServices/Dock.app/Contents/XPCServices/com.apple.dock.extra.xpc/Contents/MacOS/com.apple.dock.extra
Identifier:      com.apple.dock.extra
Version:         1.0 (1)
Build Info:      Dock-1168009000000000~1
Code Type:       X86-64 (Native)
Parent Process:  ??? [1]
User ID:         501

Date/Time:       2016-07-23 22:02:38.404 -0500
OS Version:      Mac OS X 10.8.5 (12F2560)
Report Version:  10

Interval Since Last Report:          10232 sec
Crashes Since Last Report:           2
Per-App Interval Since Last Report:  10232 sec
Per-App Crashes Since Last Report:   2
Anonymous UUID:                      DBFAB220-E500-AA92-29CA-A629725D5487

Crashed Thread:  0  Dispatch queue: 
com.apple.dock.extra.peer.0x7fbaa90309d0.xpcq

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000018

VM Regions Near 0x18:
--> 
    __TEXT                 0000000104f6a000-0000000104f6f000 [   20K] r-x/rwx 
SM=COW  
/System/Library/CoreServices/Dock.app/Contents/XPCServices/com.apple.dock.extra.xpc/Contents/MacOS/com.apple.dock.extra

Thread 0 Crashed:: Dispatch queue: com.apple.dock.extra.peer.0x7fbaa90309d0.xpcq
0   libobjc.A.dylib                     0x00007fff8d99e498 objc_msgSend_vtable3 
+ 24
1   com.apple.Foundation                0x00007fff9524b2e7 -[NSBundle 
loadAndReturnError:] + 646
2   com.apple.Foundation                0x00007fff9524b05c -[NSBundle load] + 19
3   com.apple.Foundation                0x00007fff9524bc64 -[NSBundle 
principalClass] + 39
4   com.apple.dock.extra                0x0000000104f6becc 0x104f6a000 + 7884
5   com.apple.dock.extra                0x0000000104f6c7c7 0x104f6a000 + 10183
6   libxpc.dylib                        0x00007fff946e64a2 
_xpc_connection_recv_message + 699
7   libxpc.dylib                        0x00007fff946e616d 
_xpc_connection_wakeup_recv + 165
8   libxpc.dylib                        0x00007fff946e48b4 
_xpc_connection_wakeup2 + 1799
9   libxpc.dylib                        0x00007fff946e417c 
_xpc_connection_wakeup + 145
10  libdispatch.dylib                   0x00007fff929dd0b6 
_dispatch_client_callout + 8
11  libdispatch.dylib                   0x00007fff929df29b 
_dispatch_source_invoke + 691
12  libdispatch.dylib                   0x00007fff929de305 
_dispatch_queue_invoke + 72
13  libdispatch.dylib                   0x00007fff929de448 
_dispatch_queue_drain + 180
14  libdispatch.dylib                   0x00007fff929de2f1 
_dispatch_queue_invoke + 52
15  libdispatch.dylib                   0x00007fff929e2091 
_dispatch_main_queue_callback_4CF + 220
16  com.apple.CoreFoundation            0x00007fff93192b4c __CFRunLoopRun + 1644
17  com.apple.CoreFoundation            0x00007fff931920e2 CFRunLoopRunSpecific 
+ 290
18  com.apple.HIToolbox                 0x00007fff94e9eeb4 
RunCurrentEventLoopInMode + 209
19  com.apple.HIToolbox                 0x00007fff94e9ec52 
ReceiveNextEventCommon + 356
20  com.apple.HIToolbox                 0x00007fff94e9eae3 
BlockUntilNextEventMatchingListInMode + 62
21  com.apple.AppKit                    0x00007fff91cb7533 _DPSNextEvent + 685
22  com.apple.AppKit                    0x00007fff91cb6df2 -[NSApplication 
nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
23  com.apple.AppKit                    0x00007fff91cae1a3 -[NSApplication run] 
+ 517
24  com.apple.AppKit                    0x00007fff91c52bd6 NSApplicationMain + 
869
25  com.apple.XPCService                0x00007fff92a6ad15 xpc_service_main + 
433
26  com.apple.dock.extra                0x0000000104f6b744 0x104f6a000 + 5956

Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib              0x00007fff94751d16 kevent + 10
1   libdispatch.dylib                   0x00007fff929dfdea _dispatch_mgr_invoke 
+ 883
2   libdispatch.dylib                   0x00007fff929df9ee _dispatch_mgr_thread 
+ 54

Thread 2:
0   libsystem_kernel.dylib              0x00007fff947516d6 __workq_kernreturn + 
10
1   libsystem_c.dylib                   0x00007fff944b1f1c 
_pthread_workq_return + 25
2   libsystem_c.dylib                   0x00007fff944b1ce3 _pthread_wqthread + 
412
3   libsystem_c.dylib                   0x00007fff9449c191 start_wqthread + 13

[snip]

Is "0" the top of the call stack (i.e. the most recently called 
method/function), or the bottom (where the call would eventually unwind, had it 
not crashed.) Also, does the dump for the non-main threads really help out here 
(in general), or is this usually a red herring?

FWIW, this is on MacOS X 10.8.5
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (Xcode-users@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to