___lldb_unnamed_function in a symbolicated crash log
crash-log, ios, xcode, xcode4, xcode5
Solution
I had same problem and solved it by calculating address for ___lldb_unnamed_function from iOS crash reports: atos not working as expected post.
After that run:
xcrun atos -arch armv7(s) -o Xyz.app.dSYM/Contents/Resources/DWARF/xyz Calculated_Address
Problem
I have a crash log produced on an iPhone OS 7.0.4. I have the appropriate .app and .dSYM files. When I symbolicate the crash log with Xcode 5, it shows me something like this: ``` Thread 0 Crashed: 0 MyProject 0x001df98a ___lldb_unnamed_function6108$$MyProject + 42 1 MyProject 0x001e0c49 ___lldb_unnamed_function6119$$MyProject + 9 2 MyProject 0x002928d5 ___lldb_unnamed_function8439$$MyProject + 13 3 MyProject 0x0027fa1f ___lldb_unnamed_function8072$$MyProject + 287 4 MyProject 0x0028e657 ___lldb_unnamed_function8368$$MyProject + 27 5 MyProject 0x002888d1 ___lldb_unnamed_function8257$$MyProject + 201 ``` When I symbolicate the crash log with Xcode 4, it produces the right result - it shows me the classes and methods from my application where the crash has occurred. There are no anonymous blocks involved in the stack trace. How come Xcode 4 and Xcode 5 produce different symbolicated crash logs? When I run the symbolicatecrash script in verbose mode, it shows identical results for both Xcode's: they match the correct .app and .dSYM files and both finish with these lines: ``` done. 1 binary images were found. Running /Applications/Xcode.app/Contents/Developer/usr/bin/atos -arch armv7 -l 0xd1000 -o '<PATH>/MyProject.app/MyProject' 0x002928d5 0x002888d1 0x001e0c49 0x0027fa1f 0x000d8f27 0x001df98a 0x0028e657 | got symbolicator for <PATH>/MyProject.app/MyProject, base address 4000 ```