Class, Function & line identification from crash stack-trace of debug version macOS app

Question

Created Mar ’21

Replies 2

Boosts 0

Participants 2

Hi there,
I received following stack trace(crash report attached) from a macOS app that crashed. The app was a debug version.

The app's debug version was compiled using Xcode 12.4 and DWARF + dSYM was selected.

line no 1, 19 & 20 look like this

Code Block 1   eu.synctest.SyncAppMac     	0x0000000109451d6c 0x109443000 + 60780
19  eu.synctest.SyncAppMac     	0x0000000109446e72 0x109443000 + 15986
20  eu.synctest.SyncAppMac     	0x0000000109446e44 0x109443000 + 15940

In the lines above , I can neither find class or function or line number of the actual code to be able to identify the problem.

Since this was a debug version I thought I was expecting the name of the class and function in this crash report.

Is my assumption incorrect that a debug version of the app when it crashes should have shown the information of code (class, function, line) ? - if this assumption is correct, why is the crash report not showing the same ?

How can I know the exact point in actual code to be able to figure out the cause ?

crash report

Boost

Answer 1

DTS Engineer OP

Apple

Mar ’21

Is my assumption incorrect that a debug version of the app when it
crashes should have shown the information of code (class, function,
line) ?

Not universally; it very much depends on how your build is configured.

However, if you have the .dSYM file that matches this crash report then should you be able to symbolicate it. Adding Identifiable Symbol Names to a Crash Report has a bunch of info on this.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0

Answer 2

heapsoft OP

Mar ’21

Hi, thanks for replying,

Not universally; it very much depends on how your build is configured.

So how to configure the build settings to be able to have symbolic crash report ? I want to avoid the process of symbolicating crash reports every time, until I fix the underling issue which is causing a lot of pain.

0