0

I have received a crash report in just mail that isn't symbolicated. I have tried all previous posted solutions provided related to this bug but none of them worked for me.

Example:

*** First throw call stack: (0x1827ac22c 0x1944800e4 0x1827abbe0 0x100281224 0x1836adf9c 0x182763f8c 0x182763230 0x1827612e0 0x18268cf74 0x18c0e76fc 0x18728ed94 0x10001f2b0 0x194b2aa08)

I have .app and .dSYM files with me.

Any help is greatly appreciated.

M Zubair Shamshad
  • 2,741
  • 3
  • 23
  • 45
iGW
  • 633
  • 5
  • 14
  • What command line are you using with `atos`? – trojanfoe Aug 18 '15 at 08:39
  • possible duplicate of [iOS crash reports: atos not working as expected](http://stackoverflow.com/questions/13574933/ios-crash-reports-atos-not-working-as-expected) – Kerni Aug 18 '15 at 08:47
  • Getting the same address back to me. Example : atos -o xyz.app/xyz -arch armv7 0x1827ac22c ... Result : 0x1827ac22c – iGW Aug 18 '15 at 09:03
  • Thanks @kerni for help . I don't have .crash file. I have only stack trace in mail . Your solution need .crash file for operations :- symbol address = slide + stack address - load address. – iGW Aug 18 '15 at 09:13
  • Without the start memory address of your binary on the crashing device at crash time you will not be able to symbolicate this. There is no way. – Kerni Aug 18 '15 at 09:18
  • I have only stack trace populating in mail after app crashed using ASL. – iGW Aug 18 '15 at 09:34
  • This is not enough to get the symbols, as I already mentioned. – Kerni Aug 18 '15 at 16:02

0 Answers0