Can I decode the crash data?

Question

Date/Time:       2013-05-24 21:06:11.345 +0000OS Version:      Mac OS X 10.8.4 (12E4005)Report Version:  10Crashed Thread:  0  Dispatch queue: com.apple.main-threadException Type:  EXC_BAD_ACCESS (SIGSEGV)Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000018VM Regions Near 0x18:--&gt;     __TEXT                 000000010d89a000-000000010d927000 [  564K] r-x/rwx SM&#x3D;COW  /Indy/PhoenixCE.app/Contents/MacOS/PhoenixCEApplication Specific Information:objc_msgSend() selector name: count Thread 0 Crashed:: Dispatch queue: com.apple.main-thread0   libobjc.A.dylib                         0x00007fff82c5d62f objc_msgSend_vtable9 + 471   com.apple.AppKit                        0x00007fff88842b05 +[NSScreen screens] + 8472   com.apple.AppKit                        0x00007fff88844575 +[NSScreen _zeroScreenHeight] + 443   com.apple.AppKit                        0x00007fff888b15cf _NSShapeRoundedWindowWithWeighting + 614   com.apple.AppKit                        0x00007fff888507c3 -[NSThemeFrame shapeWindow] + 3365   com.apple.AppKit                        0x00007fff888b055c -[NSThemeFrame setFrameSize:] + 4576   com.apple.AppKit                        0x00007fff888af68f -[NSWindow _setFrame:updateBorderViewSize:] + 9297   com.apple.AppKit                        0x00007fff888aee04 -[NSWindow _oldPlaceWindow:] + 11428   com.apple.AppKit                        0x00007fff888ae2b9 -[NSWindow _setFrameCommon:display:stashSize:] + 18379   com.Apple.Phoenix.UI                    0x0000000110580045 -[GUIMainController shuffleWindow] + 1477 (GUIMainController.mm:470)10  com.Apple.Phoenix.UI                    0x0000000110586aef -[GUIPeriodicController periodic:] + 2399 (GUIPeriodicController.mm:219)11  com.apple.Foundation                    0x00007fff86867463 __NSFireTimer + 9612  com.apple.CoreFoundation                0x00007fff81df5804 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 2013  com.apple.CoreFoundation                0x00007fff81df531d __CFRunLoopDoTimer + 55714  com.apple.CoreFoundation                0x00007fff81ddaad9 __CFRunLoopRun + 152915  com.apple.CoreFoundation                0x00007fff81dda0e2 CFRunLoopRunSpecific + 29016  com.apple.HIToolbox                     0x00007fff83dc6eb4 RunCurrentEventLoopInMode + 20917  com.apple.HIToolbox                     0x00007fff83dc6b94 ReceiveNextEventCommon + 16618  com.apple.HIToolbox                     0x00007fff83dc6ae3 BlockUntilNextEventMatchingListInMode + 6219  com.apple.AppKit                        0x00007fff8887f533 _DPSNextEvent + 68520  com.apple.AppKit                        0x00007fff8887edf2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 12821  com.Apple.Phoenix.UI                    0x0000000110594b52 processUIEvent() + 290 (PhoenixCECocoaGUI.mm:363)22  com.Apple.Phoenix.UI                    0x000000011058e152 Phoenix::Core::UICocoaImpl::processEvent() + 44 (UICocoaImpl.mm:61)23  com.Apple.PhoenixCE                     0x000000010d8ae62e main + 2302 (mainer.cpp:180)24  com.Apple.PhoenixCE                     0x000000010d89b604 start + 52:::::::::::::::::::::::::::::Thread 0 crashed with X86 Thread State (64-bit):  rax: 0x000000000000000f  rbx: 0xffffffffffffffff  rcx: 0x0000000001010101  rdx: 0x0000000000000001  rdi: 0xffffffffffffffff  rsi: 0x00007fff7268ea80  rbp: 0x00007fff523631b0  rsp: 0x00007fff52363028   r8: 0x00007fff72435a30   r9: 0x00007fff72435a01  r10: 0x0000000000000000  r11: 0x00007f968c000600  r12: 0x0000000000000000  r13: 0x0000000000000000  r14: 0x0000000000000001  r15: 0x000000000000000c  rip: 0x00007fff82c5d62f  rfl: 0x0000000000010206  cr2: 0x0000000000000018Logical CPU: 1

Camelot · Accepted Answer

There&#x27;s very little you can discern from this log without access to the source code.The crash log identifies which part of the code crashed, but without the source code it&#x27;s almost impossible to translate that into any kind of actionable item.The problem is compounded by the fact you&#x27;re crashing deep in Apple&#x27;s core code due to an invalid address issue, which most often happens because of something else in the code, such as a data structure not being initialized or being setup incorrectly, so even knowing the speciifc line of code may not help without more context.So, in short, unless you&#x27;re a developer, this log isn&#x27;t going to help you an awful lot.

MrHoffman · Answer

Assuming this is your application code — if this is not your source code, please see Camelot&#x27;s reply — here is a dump of a few of my crash-related bookmarks...Start with these two...http://www.sealiesoftware.com/blog/archive/2008/09/22/objc_explain_So_you_crashe d_in_objc_msgSend.htmlhttp://www.raywenderlich.com/10209/my-app-crashed-now-what-part-1Some other semi-related discussions.http://developer.apple.com/library/ios/#technotes/tn2151/_index.htmlhttp://briksoftware.com/blog/?p&#x3D;130http://developer.apple.com/library/mac/#technotes/tn2004/tn2123.htmlSome tools, though a little stale...http://www.red-sweater.com/blog/860/crash-reporter-roundupIf you&#x27;re a registered developer, the developer forums are definitely a better spot for this question.  Developers also have access to materials including the Apple WWDC videos, and there are videos related to crash reporting.If you&#x27;re not the developer, check with the folks supporting this tool, or try a different tool.

ANRV · Answer

Thankyou for the responses. I am a new Mac developer. I have the access to the source code but I could not quite get from the crash log which part of the code do I have to start looking at.I see that the threads1,2,3 executes and then there is a crash in thread0 i.e the main thread. Does this mean that the the invalid memory was accessed somewhere in the last few lines or it could be anywhere in the whole thread0 execution?19  com.apple.AppKit                        0x00007fff8887f533 _DPSNextEvent + 68520  com.apple.AppKit                        0x00007fff8887edf2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 12821  com.Apple.Phoenix.UI                    0x0000000110594b52 processUIEvent() + 290 (PhoenixCECocoaGUI.mm:363)22  com.Apple.Phoenix.UI                    0x000000011058e152 Phoenix::Core::UICocoaImpl::processEvent() + 44 (UICocoaImpl.mm:61)23  com.Apple.PhoenixCE                     0x000000010d8ae62e main + 2302 (mainer.cpp:180)24  com.Apple.PhoenixCE                     0x000000010d89b604 start + 52Any help would be appriciated.Thanks in advance.

xnav · Answer

Look at the crash log under the Devices tab of Xcode Organizer and Re-symbolicate if necessary to turn these23  com.Apple.PhoenixCE                     0x000000010d8ae62e main + 2302 (mainer.cpp:180)24  com.Apple.PhoenixCE                     0x000000010d89b604 start + 52lines into something more meaningful.

ANRV · Answer

I got the logs from the test enggineers and the problem is not easily reproducible. Hence, I dont see that I can use Xcode to look at the crash logs.Does this mean that the issue is somewhere around the code 23  com.Apple.PhoenixCE                     0x000000010d8ae62e main + 2302 (mainer.cpp:180)24  com.Apple.PhoenixCE                     0x000000010d89b604 start + 52or can it be anywhere else too?Thanks.

MrHoffman · Answer

I&#x27;d guess that a message was sent to a corrupted object pointer or to a deallocated object — that&#x27;s what the call to objc_msgSend does — but do symbolicate the dump.  (See the first link posted, above.  The programmer that wrote article knows that subject matter, too.)You will use Xcode to symbolicate the dump and keep the symbol file around, and that&#x27;ll help figure out what happened while using Xcode.  Keeping the symbols around for a build intended for testers or for release is common practice.  (Some of that is discussed in the links posted earlier.)