I'm trying to symbolize a crash dump for an iOS app boot using Xamarin.iOS. I see a lot of warning about the binary images of the system such as not being able to find symbols for a foundation, and symbolically the output is ultimately missing most of the information I need.
I described the following procedure, I have put MyApp.app, MyApp.app.dSYM, and crash log in a directory and symbol -o crash.txt "crashreport.crash" "MyApp The app has run "
. Output is not a symbol in crash.txt, and I see many errors in the signal console output. For example:
Finding symbol: symbol file for foundation .fetching - [undef ] [] Searching ... ... are not matching with the e596bd80bcc83f15aca36a7ef014f457 special program for dsym with UUID running mdfind "com_apple_xcode_dsym_uuids == E596BD80-BCC8-3F15-ACA3-6A7EF014F457" @dsym_paths = () @exec_names = () for dsym ## The warning did not get executable: unstripped any Variant does not match the version of KB / System / Library / Frameworks / Foundation.framework / Foundation
Full production
Confirm this Dump that is used to dwarfdump the same as that in a UUID crash in MyApp.pSYM.
I am using Xamarin Studio 5.7.1 on Xcode 6.1.1.
Can anyone suggest what is going wrong?
After
Apple's symbolicate tool that lets you query for symbols Special program databases require adding all executable and match-o binary.
It is a difficult task that is needed. How do I remove from the list, or know that the queue has been completed and the binary indexed with its UUID can never be found
. I wrote this symbolic pro device
Here is a program I wrote for the testfree (company). It is called symbolic-supporter and there are some important differences which are the symbol of Apple:
- No indexing is required.
- You can specify the directory where your iOS symbols are located 10x faster.
- It is.
- And if you can compile for otool another OS, it can run on other platforms besides the Mac. TestFairy uses it for production and updates when the iOS crash report changes.
You can get it here on github:
Hope it helps;)
No comments:
Post a Comment