# OS X Crash Report Symbolication

DevFeed: [OS X Crash Report Symbolication](<https://devfeed.tech/articles/os-x-crash-report-symbolication-25390.md>)

Original publisher: [Read original article](<https://smileykeith.com/2013/08/09/os-x-crash-symbolication/>)

Author: Keith Smiley

Published: 2013-08-09T20:26:00Z

Content type: tutorial

Language: en

Sources: [Keith Smiley](<https://devfeed.tech/sources/keith-smiley.md>)

Topics: [macOS](<https://devfeed.tech/topics/macos.md>), [Xcode](<https://devfeed.tech/topics/xcode.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>), [x86](<https://devfeed.tech/topics/x86.md>)

Tags: [apple](<https://devfeed.tech/tags/apple.md>), [build](<https://devfeed.tech/tags/build.md>), [command-line](<https://devfeed.tech/tags/command-line.md>), [crash](<https://devfeed.tech/tags/crash.md>), [crashlytics](<https://devfeed.tech/tags/crashlytics.md>), [issue](<https://devfeed.tech/tags/issue.md>), [macos](<https://devfeed.tech/tags/macos.md>), [x86-64](<https://devfeed.tech/tags/x86-64.md>), [xcode](<https://devfeed.tech/tags/xcode.md>)

## AI overview

This article explains how to symbolicate OS X crash reports for a macOS application when the issue cannot be reproduced. It describes using the archived build's dSYM file, the application's x86_64 architecture, and the crash report's load address to identify the application methods involved.

## Source excerpt

As you may know I write a small OS X called Sail. Over the past few months that it has been available I've received a few crash reports about an issue I wasn't able to reproduce. Today I decided I wanted to dive into them and see if I could at least figure out the root of the issue and fix it with my next release. This lead me down the rabbit hole of symbolication, something I personally hadn't dealt with myself before (since Crashlytics does it for you). I was hoping I would be able to find something around the internet about this, unfortunately what I mostly came up with was a lot of iOS related answers that didn't seem to work the same way and two links to Apple documentation that have been removed. Other than the process for symbolicating reports for OS X apps seems to be different than iOS apps which there is plenty of documentation for (I'm not bitter). Daniel Jalkut has a post about these but his exact method didn't seem to work for me. Here is what did work for me. For my first abridged crash report I had this Process: Sail [35072] Path: /Applications/Sail.app/Contents/MacOS/Sail Load Address: 0x106823000 Identifier: com.keithsmiley.SailOSX Version: 4 (1.2.0) Code Type: x86_64 (Native) Parent Process: launchd [207] Date/Time: 2013-07-19 16:09:24.097 +0200 OS Version: Mac OS X 10.8.4 (12E55) Report Version: 8 Thread 0: 13 Accounts 0x00007fff839fd1b1 -[ACAccountStore accountTypeWithAccountTypeIdentifier:] + 230 14 Sail 0x00000001068308f7 15 Sail 0x0000000106830798 16 Sail 0x0000000106825249 17 CoreFoundation 0x00007fff82465eda _CFXNotificationPost + 2554 18 Foundation 0x00007fff8611b7b6 -[NSNotificationCenter postNotificationName:object:userInfo:] + 64 31 AppKit 0x00007fff812cc1a3 -[NSApplication run] + 517 32 AppKit 0x00007fff81270bd6 NSApplicationMain + 869 33 libdyld.dylib 0x00007fff869d07e1 start + 0 Binary Images: 0x106823000 - 0x106896fff com.keithsmiley.SailOSX (1.2.0 - 4) <D1F313B6-21F6-341B-8627-5480C5D1DB20> /Applications/Sail.app/Contents/MacOS/Sail