Parse.com crash report: stack trace not marked

We are using Parse.com crash report. It was easy to integrate downloading symbol information (success message in a log file), and crash reports were sent to Parse.com.

However, the stack trace contains malformed names and does not contain line information for our own code, as if we were not loading symbol information, for example:

0    CoreFoundation    __exceptionPreprocess @ 0x84
1    libobjc.A.dylib   objc_exception_throw @ 0x38
2    CoreFoundation    -[NSException raise] @ 0x8
3    MyApp             _TToFC9MyApp23TestViewController13viewDidAppearfS0_FSbT_ @ 0x1f4
4    UIKit             -[UIViewController _setViewAppearState:isAnimating:] @ 0x24c

Downloading symbolic information was successful. Otherwise, a warning will be indicated in the crash report: this stack trace is asymmetric. To get characters ... But we don't get this warning.

Maybe this is due to some compiler settings in release mode (we only load symbols for releases)? Or what could be the reason for tracing asymmetric stacks?

+4
source share
3 answers

I assume you are using Swift? - If so, then there is a wonderful Mike Ash blog post about why and how this happens: https://mikeash.com/pyblog/friday-qa-2014-08-15-swift-name-mangling.html

You can also untie the names by starting the terminal and starting xcrun swift-demangle SYM- but you need to do this in the same version of the Quick compiler when you compiled the application.

Thanks Dan

+3
source

Try setting Debug Debug characters. While copying to No:

, , NO : " " " "

enter image description here

, , .

+2

My two cents is that you are sending a message to a freed object, but you cannot be sure without a full stack trace.

+1
source

All Articles