Microstackshots crash log is not symbolicated correctly
Originator: | vytis.s.lt | ||
Number: | rdar://46591102 | Date Originated: | 10-Dec-2018 12:16 PM |
Status: | Open | Resolved: | |
Product: | iOS + SDK | Product Version: | 10.0 (10A255) |
Classification: | UI/Usability | Reproducible: | Always |
Summary: Crash logs on device that show too many wakeups are not symbolicated. Trying to do it with symbolicatecrash command fails even with correct symbols available. Steps to Reproduce: 1. Get a crashlog from device that shows number of wakeups during some period of time 2. Try to read it Expected Results: 3. It should be symbolicated Actual Results: 3. It is not fully symbolicated. Version: 10.0 (10A255) Notes: Trying out manual symbolication with symbolicatecrash command does not help: DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer/ /Applications/Xcode.app/Contents/SharedFrameworks/DVTFoundation.framework/Versions/A/Resources/symbolicatecrash not_symbolicated.crash path/to/dSYMs > symbolicated_crash.crash Some of the methods in the stacktrace just contains UUID of library: 2 ??? (<2151A33A-068D-37FE-ACB5-02E0BB7DA9D8> + 264960) [0x103758b00] It’s possible to edit the crashlog to make it work with symbolicatecrash: 1. Find what library each UUID corresponds to (from other crash logs or symbols) 2. Replace corresponding <UUID> with name of the framwork in the crash log (e.g. <2151A33A-068D-37FE-ACB5-02E0BB7DA9D8> -> avs) 3. Add framework name and path in “Binary Images” section at the end of the crashlog 4. Run symbolicatecrash as outlined above Attaching three crash logs: original, after fixing and after symbolication. Attaching symbols for avs and Wire to allow symbolication.
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!